Repository navigation
docs: the packaging trigger's intended shape at M6 - #65
Merged
Merged
Conversation
… measurements Signed-off-by: Ayla Croft <aylacroft@proton.me>
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
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.
Records, beside the change-log line for the gate's release check, what the packaging trigger should become when M6 makes signed artifacts the deliverable: a scheduled
packageonmainrather than a per-branch one. Carries the owner, the lift condition (the first M6 slice producing a signed artifact) and the measurements the comparison rests on (16 min for a three-OS run, 52 s cold / 2 s warm forprod_check.sh, free runners because the repository is public).ROADMAP only; no code, and no packaging path touched, so this runs the four checks and no package build.