Async local nuget server delivery and local nuget trigger
When you want to run two builds where one of them deliver nuget package for next one - the next one pick up the older package - its because new nuget package will be visible after the first build signal ends (async). So work around is to run the next one by Nuget Trigger. In this case I face with problem to make it working under 2017.1.2 (build 46812) against local nuget server. Do you have any working example?
Please sign in to leave a comment.
Hi Piotr,
How are you publishing the Nuget package? If you use the "Nuget Publish", it should be synchronously added to the build so it's available for the next one. (This feature was introduced in 2017.1)