Separate NuGet Restore for Appveyor build #525
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikkelbu
approved these changes
Jan 5, 2019
|
Definitely hacky - but better than 'previous' because 'previous' will break on the next appveyor update, when the current build becomes the previous. Fingers crossed, this 'fix' will keep working indefinitely. 🙂 |
|
@IlyaFinkelshteyn sure one could have a |
|
Thanks both! Will take a look. 🙂 |
This was referenced Feb 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following on from: #517, @IlyaFinkelshteyn from the @appveyor team found this solution, which will allow us to continue using the current appveyor image, and our builds not to fail when the "Previous" image next changes.
The core issue seems to be this one: NuGet/Home#7414, which Appveyor are tracking via: appveyor/ci#2787