-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Separate build ID from ProwJob ID for Jenkins jobs
It is the intent in the `initupload` and `sidecar` container utilities to use the full information provided by Prow to the job in `$JOB_SPEC` to determine where in GCS artifacts from the job should be pushed. Right now, this is possible and useful for jobs triggered using `plank` but not so for those triggered using `jenkins-operator`. The largest issue is that for Jenkins builds, the `$BUILD_ID` parameter was being used as an identifier to allow Prow to correlate builds with ProwJobs, whereas in `plank` pods the parameter was a monotonically increasing identifier vended by `tot` used for e.g. GCS. This patch introduces the `$PROW_JOB_ID` variable and field to the job spec to separate these two concerns and allow for them to be fulfilled together. We also thread through links so that user-facing pages use the `$BUILD_ID` identifier and not the `$BUILD_NUMBER` identifier that Jenkins produces. This also handily solves issues with loss of state or Jenkins inconsistencies by allowing the source of truth for job build state to live in `tot`. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
- Loading branch information
1 parent
1281b60
commit 3539019
Showing
14 changed files
with
237 additions
and
115 deletions.
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.