jobs/build-mechanical: schedule at off-peak and run builds serially #1076
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
Adjust the cron schedule trigger to start at 2am UTC every day to run this job at off-peak times. Also, run the scheduled builds serially by waiting for each build to finish before starting the next one.
dustymabe
reviewed
Dec 20, 2024
| ] | ||
| try { | ||
| echo "Triggering build for mechanical stream: ${it}" | ||
| build job: 'build', wait: true, parameters: [ |
There was a problem hiding this comment.
I think we can add propagate: false and we won't need a try/catch here.
https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/
There was a problem hiding this comment.
Ah, good point! That does seem like it'll be a simpler solution.
marmijo
added a commit
to marmijo/fedora-coreos-pipeline
that referenced
this pull request
Dec 20, 2024
Instead of the try/catch block, use `propagate: false` instead to wait for the build to complete before moving on to the next one. follow-on to: coreos#1076
marmijo
added a commit
to marmijo/fedora-coreos-pipeline
that referenced
this pull request
Dec 20, 2024
If a scheduled build fails, the build-mechanical job will fail. Instead of the try/catch block to solve this, use `propagate: false` instead to build each scheduled stream regardless of the build result. follow-on to: coreos#1076
dustymabe
pushed a commit
that referenced
this pull request
Dec 21, 2024
If a scheduled build fails, the build-mechanical job will fail. Instead of the try/catch block to solve this, use `propagate: false` instead to build each scheduled stream regardless of the build result. follow-on to: #1076
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.
Adjust the cron schedule trigger to start at 2am UTC every day to run this job at off-peak times. Also, run the scheduled builds serially by waiting for each build to finish before starting the next one.