[RelEng] Keep up to ten builds of the Promotion/Publication jobs #3235
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
This way at least one release cycle is available in the history, as these jobs run at least six times per release.
Member
Author
|
This is a pure RelEng change that's intended to be used for tomorrows RC1 promotion. Therefore I'm submitting this now despite we are currently in a freeze-period. |
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.
This way at least one release cycle is available in the history, as these jobs run at least six times per release (M1, M2, M3, RC1, RC2 and R/GA).
Also extend the timeout for the publication job, which runs usually at most 7min (for a release), to 45min. This is safety factor is similarly high to the promotion-job (which runs about 20min max and has a 120min timeout, as I don't want to have a promotion/publication aborted, just due to a slow network or busy Jenkins.