ci: avoid installing the toolchain from scratch in each job #257
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
Contributor
Author
|
CI is failing because the default token for PRs does not allow pushing to the registry. See a run in my fork: https://github.com/umarcor/f4pga-examples/actions/runs/1878523142 (which uses |
umarcor
force-pushed
the
ci-packages
branch
2 times, most recently
from
8199e14 to
4988e0c
Compare
umarcor
force-pushed
the
ci-packages
branch
2 times, most recently
from
e305549 to
c21bdd4
Compare
* Use GitHub Packages * Use container in a step, instead of a container job F4PGA_INSTALL_DIR changed to an absolute location due to actions/runner#1525 Signed-off-by: Unai Martinez-Corral <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Instead of installing the toolchain in each job, this PR splits CI in two stages. First, the 18 variants of the toolchain are installed in containers, which are pushed to GitHub Packages. Then, example jobs pull the containers/packages and use them straightaway.
BTW, a container step is used instead of a container job, so that
actions/checkoutis executed on the "host".