AppVeyor does not handle ASP.NET vNext Nuget Packages
If you take a look at https://ci.appveyor.com/project/Alxandr/yolodev-unpak/build/1.0.0-b... you'll see that I try to add a NuGet package as an artifact. This crashes the build because AppVeyor doesn't like the nuget package. If you go back a few versions in the build (https://ci.appveyor.com/project/Alxandr/yolodev-unpak/build/1.0.0-b...) you will see that this problem is probably due to NuGet.exe not liking the new vNext packages either (though I've been told that this has been fixed, just not released yet).
Is this something you can fix so that I can get my builds running again?
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 03 Nov, 2014 02:43 AM
Interesting. Do you have a link to an issue or blog discussing that?
2 Posted by Alxandr on 03 Nov, 2014 02:58 AM
Sorry, but I can't find any. Though me and David Fowler was just discussing the issue over at https://jabbr.net/#/rooms/AspNetvNext. Also, Fowler just told me that they had the same problem with MyGet initially, and they contacted them to have them fix it. He also suggested I build nuget.exe from source and use that, but doing so in every build seems unnecessary if the issue can rather be resolved.
Support Staff 3 Posted by Feodor Fitsner on 03 Nov, 2014 04:21 AM
I've looked through the conversation...no hints so far... but will check why it crashes. Btw, NuGet Package Explorer crashes too on this package.
4 Posted by Alxandr on 03 Nov, 2014 05:42 AM
Yeah. The reason is probably quite simple. There are two frameworks,
aspnetcore50, which both NuGet doesn't know about and classifies as "unknown". Both depend on the same package, so NuGet thinks there's a duplicate dependency (you can see the actual error on the earlier build I linked). At least that's what I've concluded, though I might be mistaken.
Support Staff 5 Posted by Feodor Fitsner on 03 Nov, 2014 05:50 AM
What package do they both depend on?
6 Posted by Alxandr on 03 Nov, 2014 05:51 AM
The following two commits are probably the solution:
Fixed casing: http://nuget.codeplex.com/SourceControl/changeset/1f2cd34d2d7fb16fb...
Added support for aspnet50 and aspnetcore50: http://nuget.codeplex.com/SourceControl/changeset/4cb251a5bfe27f871...
7 Posted by Alxandr on 03 Nov, 2014 05:53 AM
As you can see from the source at https://github.com/YoloDev/YoloDev.UnpaK/blob/master/src/YoloDev.Un... they both depend on
Microsoft.Framework.Runtime(which is the only dep that isn't a build-time only dep).
Support Staff 8 Posted by Feodor Fitsner on 03 Nov, 2014 06:02 AM
Looks like that, thank you for the hint! Now compiling from sources is the only way to go :)
9 Posted by Alxandr on 03 Nov, 2014 06:09 AM
You're saying you're compiling from sources, or that I should do that in all my vNext repos?
Support Staff 10 Posted by Feodor Fitsner on 03 Nov, 2014 06:26 AM
I mean we should compile from sources the latest NuGet version to be able to work with vNext NuGet packages. I'll add an issue for that.
11 Posted by Alxandr on 03 Nov, 2014 07:16 AM
Will you notify me when you've updated to a new version of NuGet?
Support Staff 12 Posted by Feodor Fitsner on 03 Nov, 2014 07:21 AM
Support Staff 13 Posted by Feodor Fitsner on 04 Nov, 2014 04:43 AM
AppVeyor has been updated on server side. You should now be able to push vNext NuGet packages to AppVeyor. However,
nuget.exeon build workers is not yet updated - just grab it from nuget.org during the build.
Let me know if you find any issues.
14 Posted by Alxandr on 04 Nov, 2014 10:08 PM
Deployment still does not work: https://ci.appveyor.com/project/Alxandr/yolodev-unpak/deployment/33598
Also, what do you mean just download
nuget.org? Do you have an address? Cause the one I got from nuget.org does not support vNext either :-/.
It's hard to live on the edge ^^
Support Staff 15 Posted by Feodor Fitsner on 04 Nov, 2014 10:14 PM
Ah, deployment - good catch! :) We have to update nuget.exe on AppVeyor worker roles too.
Btw, deployment details are not visible to other accounts, so the link https://ci.appveyor.com/project/Alxandr/yolodev-unpak/deployment/33598 is not working.
16 Posted by Alxandr on 04 Nov, 2014 10:29 PM
Hmm. I figured you being admin would be able to see the content. The error is the same though, duplicate dependencies.
Support Staff 17 Posted by Feodor Fitsner on 04 Nov, 2014 10:31 PM
Got it. Will fix that with the next deployment.
18 Posted by Alxandr on 04 Nov, 2014 10:32 PM
Perfect :). Again, I'd be really appreciative if you'd let me know when it's supposed to be working :).
Also, I'd just like to say that the support you provide here is really great. The response times are small, and normally you fix problems within hours. I'm really amazed by the work you do :)
Support Staff 19 Posted by Feodor Fitsner on 06 Nov, 2014 05:25 AM
OK, AppVeyor with NuGet 2.8.3 has been deployed. Deployment of ASP.NET vNext packages should be working now.
20 Posted by Alxandr on 06 Nov, 2014 07:05 PM
Hi, my build just failed to upload the artifacts again: https://ci.appveyor.com/project/Alxandr/yolodev-unpak/build/1.0.0-b...
Support Staff 21 Posted by Feodor Fitsner on 06 Nov, 2014 07:12 PM
What was OS image, default?
22 Posted by Alxandr on 06 Nov, 2014 07:14 PM
2012 R2. Unchanged. It worked yesterday, it worked on my other project build which kicked off at almost the same time.
Support Staff 23 Posted by Feodor Fitsner on 06 Nov, 2014 07:18 PM
We did another deployment yesterday, but that part wasn't changed.
24 Posted by Alxandr on 06 Nov, 2014 07:43 PM
Just rebuilding made it work. So my guess would be something along the line of not all servers beeing updated or something.
Support Staff 25 Posted by Feodor Fitsner on 06 Nov, 2014 07:50 PM
I can't believe that! :) It's two web roles in Azure Cloud Service! We've seen many Azure-related glitches, but unsynced CS roles...
Let's think for now it's sporadic error. Let me know if you catch it again.
26 Posted by Alxandr on 06 Nov, 2014 08:42 PM
Yeah. Btw, which commit did you use to build nuget? I'm trying to build it myself, but I can't get it to work.
Support Staff 27 Posted by Feodor Fitsner on 06 Nov, 2014 09:04 PM
We haven't built it. It's the latest 2.8.3 available on NuGet and CodePlex download that includes vNext support.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:49 AM.