Revive cache upload mechanism and CI-related cleanup #267
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
bkotzz
approved these changes
Oct 5, 2020
| if "%BRANCH_NAME%" == "master" ( | ||
| python jenkins.py --upload |
There was a problem hiding this comment.
jenkins.py could use a rename these days
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.
The workflow for adding/updating a Hunter package has changed considerably with #250 (thank you @drodin!). Now, a separate branch to keep track of the tested toolchains and their results is no longer needed as a Github Pages page will be automatically updated with any new commit to master. Subsequently, I removed the old verbiage in the readmes and templates that referred to the Travis/AppVeyor/hunter-testing workflow.
With Github Actions it is now very easy to upload build cache when a merge to master occurs. As such, I worked out the nuances with Python versions across all the action templates and added a couple of newer toolchains in this PR. When a merge to master occurs, both the Github Pages page and the new Hunter cache repository at https://github.com/cpp-pm/hunter-cache will be updated automatically.
I will be pushing "updates" to all packages to generate their pages and cache updates. This closes #216.