jobs/fix-build: new job to fix archived builds #1003
Merged
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
No functional change. Prep for next patch.
Very often, our pipeline flakes after the final archiving stage, e.g. if the fedora-messaging queue is down, or Robosignatory is backed up. Ideally, as discussed in coreos#566, we could just rerun the job and have it know to salvage the builds, but there's a lot of details there that we need to get right. (And... it's probably not worth tackling if we're eventually moving away from Jenkins anyway.) For now at least, it's not hard to just have a separate job that reruns those last final steps from the `build` and `build-arch` jobs so we can salvage those builds. You need to know what you're doing when using this job. It should only be used when strictly necessary. It's often better to just do a new build instead. Fixes: coreos#566
This was referenced Jun 18, 2024
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.
Very often, our pipeline flakes after the final archiving stage, e.g. if
the fedora-messaging queue is down, or Robosignatory is backed up.
Ideally, as discussed in #566, we could just rerun the job and have it
know to salvage the builds, but there's a lot of details there that we
need to get right. (And... it's probably not worth tackling if we're
eventually moving away from Jenkins anyway.)
For now at least, it's not hard to just have a separate job that reruns
those last final steps from the
buildandbuild-archjobs so we cansalvage those builds.
You need to know what you're doing when using this job. It should only
be used when strictly necessary. It's often better to just do a new
build instead.
Fixes: #566