build(pipeline caching): Add pipeline package caching for nuget and libman #788
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
Add CacheBeta task to azure-pipelines.yml to enable NuGet package caching and hopefully speed up CI builds. Enable creation of packages.lock.json for projects built in pipeline to enable above.
May be encountering this issue: microsoft/azure-pipelines-tasks#11449 Suggested workarounds taken from this comment: NuGet/Home#7921 (comment)
…les by Directory.Build.Props
…to be able to update the package lock files as a developer
…e used in an integrationtest scenario
…therwise try deploying embedded vstest binaries
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Fix #667
Supersedes #767