Switch vcpkg cache for Windows build check to NuGet #103
Conversation
This file contains hidden or 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
Both vcpkg and GitHub removed support for GitHub Actions Cache, so the current best way of caching packages on Windows is via NuGet.
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.
Both vcpkg and GitHub removed support for GitHub Actions Cache, so the current best way of caching packages on Windows is via NuGet.
Uses a classic PAT in my account to access the package repository. The token is added as a secret in the projectM org.
Sadly, passing secrets to jobs triggered by a PR from a forked repository (like this one here) doesn't work, so these build checks will still take ~15mins. Push and post-merge builds will run faster though.