releng: run omicron-package with --only (and other small fixes)
#7150
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
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.
This is a late follow-up to #5799 that I've had lying around in a branch for a while. We now instruct omicron-package to instruct Cargo to only build the binaries we actually want for that particular stage of the releng process. This has the effect of allowing the OS images to build while Cargo is busy building Nexus, for instance.
This does not improve the speed for the CI job significantly, but does show some improvements in local incremental rebuilds. There is some straggling time once the TUF repo is built running
cargo xtask verify-libraries --releasethat can reduce time-to-TUF-repo by a few more minutes by making our check there more correct (see #7149).