update_chroot: introduce '--setuponly' flag#178
Merged
Conversation
Currently the os/sdk and os/toolchains job perform a chroot update whose results are immediately discarded because the rest of the build uses a fresh chroot and catalyst. Towards the end of a release period this can extend the build time by about an hour (longer if rust is involved). Introduce a `--setuponly` flag that bails after the chroot configuration, and the skips chroot update. Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
pothos
approved these changes
Oct 25, 2021
Member
Author
|
CI passed with just a test-flake (reran). Merging. |
t-lo
pushed a commit
that referenced
this pull request
Apr 17, 2023
sys-devel/gettext: sync with gentoo upstream
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
add setuponly mode to update_chroot
update_chrootis called at the beginning of all of our jobs, but not all of them need an updated chroot.sdkandtoolchainsjobs use catalyst, and run in a nested chroot from a fresh extracted tarball. It can take even an hour to update the chroot. Use the--setuponlyflag to only configure portage and repos.Testing done
Started two builds for comparison.
CI with this branch:
http://jenkins.infra.kinvolk.io:8080/job/os/job/manifest/3949/
CI without this branch:
http://jenkins.infra.kinvolk.io:8080/job/os/job/manifest/3950/