Self hosted runner #493
Merged
Self hosted runner #493
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
We started experiencing timeouts on the default GitHub runners due to the lengthy setup time for the Yocto build environment. This change modifies the main CI workflow to utilize a self-hosted runner that has less computing limitations.
Speed up the pipeline by reusing the Yocto download and sstate cache directories on the self-hosted runner via NFS mounts. Mostly for `devtool modify busybox` which needs to build quilt-native and a few other recipes.
The self-hosted runner is already configured to allow unprivileged user namespaces, contrarily to the default GitHub-hosted runners. Therefore, this step is not needed and can be removed.
The packages are already installed on the self-hosted runner.
The self-hosted runner reuses the workspace after each workflow. This means we now need to clean up after ourselves to avoid polluting the workspace for the next run. We keep it on failure to allow debugging.
We now separate the timeouts for bitbake commands that just do some parsing, and those that do actual builds.
This test needs to initiate the bitbake parser, which can take a while and the previous timeout was too low and failed.
deribaucourt
force-pushed
the
self-hosted
branch
from
fa10de5 to
96251f7
Compare
It looks like the actions rules now trigger for pull request and push on the pull request branches, causing double runs for PRs. There's only a need to run on push to main branches.
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.
Linked to #492
I configured a new self-hosted runner that shouldn't timeout. It has a beefier CPU, disk and no time restriction.
Also has a Yocto SSTATE cache, so it makes less demands and takes less time.