-
-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Implement a C.I build #77
Comments
I've started working on this, however I've hit an issue with Basically I'm running:
However
Any ideas? The full log is available if that helps? |
@mattwarren, i think you should use |
@mattwarren You need another nuget feed for .NET Core packages. In .nuge\NuGet.config you can find the whole list. You can run: |
@mattwarren Another problem you probably will face is dnx/dotnet cli differences. In general VS is still using dnx to build all project.json-based solutions (switch to dotnet cli is planned for RC2). And I am not sure if xUnit runner supports dotnet cli at all. How I do "core CI things" at work:
@AndreyAkinshin I think that we should also add some CI for Mono. It would be great if your verification before nuget package release could be 100% automated. |
Thanks to both of you for the tip about However I now have a problem related to MsBuild, seems like MsBuild 12.0 isn't installed:
|
I was planning to just use But if it's the only way I'll use those instructions, thanks for them |
Is it possible to have AppVeyor instance with VS 2013 and VS 2015? Please let me know if you have any other problems. |
I've looked at this a bit more:
AppVeyor uses a VS 2015 image by default, but I also tried VS 2013 and got the same issue. |
Could you try net45 instead 451? And also net46? |
|
I have simplified the dependencies by removing dependency to NETStandard.Library which is just huge a set of packages. Now the restore should be much more faster. But I don't know what to do with the C.I. Perhaps we could try to use Team City? It is possible to get the license for free for OSS projects. If you don't mind I can register BDN and set up few build configurations: classic, dnx and core. What do you guys think? @mattwarren @AndreyAkinshin |
@adamsitnik sorry I missed this comment.
Fine by me, as long as one way or the other we get a C.I build, I don't mind which technology we use. I was only playing around with AppVeyor because I'd used it before. |
There's a nice working AppVeyor here that we can use: https://ci.appveyor.com/project/StackExchange/dapper-dot-net |
OK, now with #187 we have no more dnx dependencies, @mattwarren you should be able to restore, build and run tests with dotnet cli. You can take a look at the scripts that I wrote |
Maybe using AppVeyor, i.e. like this https://ci.appveyor.com/project/mattwarren/minibench-warren. This way if someone (probably me) breaks the build or some tests, we'll know about it sooner rather than later
See this discussion for some background and extra info.
The text was updated successfully, but these errors were encountered: