ci: build: build LXA TAC images on our (experimental) self hosted runner #158
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
hnez
force-pushed
the
forrest
branch
8 times, most recently
from
13a0065 to
ed793ee
Compare
The jobs run in a virtual machine with an ephermal disk image,
much like the official runners do.
There are however two differences:
- The virtual machine has a lot more RAM, CPU cores and disk space
than the official runners.
- The disk image _can be_ persisted. The job just needs to know the
correct secret token.
The jobs are set up so that jobs running on the local scarthgap branch
persist their disk images on success, but jobs from pull request do
not and can not.
This means jobs from pull requests and jobs on the scarthgap branch
will use a disk image based on the latest successful run on the
scarthgap branch.
This gives us near-incremental build speeds while preventing broken
build or builds from pull requests from tainting our runner's disk.
Since the runner will not be available in forked repositories the job will
only attempt to run if the HAS_BUILD_RUNNER repository variable is set
to 'true'.
Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
jluebbe
approved these changes
Jul 31, 2024
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 jobs run in a virtual machine with an ephermal disk image, much like the official runners do.
There are however two differences:
The virtual machine has a lot more RAM, CPU cores and disk space than the official runners.
The disk image can be persisted. The job just needs to know the correct secret token.
The jobs are set up so that jobs running on the local scarthgap branch persist their disk images success, but jobs from pull request do not and can not.
This means jobs from pull requests and jobs on the scarthgap branch will use a disk image based on the latest successful run on the scarthgap branch.
This gives us near-incremental build speeds.
TODO before merging: