S3 URLs are not unique if build numbers are reused
Bug #1449154 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-ci-tools |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When we restore a Jenkins job from a backup, we need to then increment the build bumber in nextBuildNumber to ensure we don't overwrite a build between backups.
One way we might do this is ci-dirctor could refuse to adopt any build stored in s3. The other route would be script a script that reported when a build number is being reused. People can use the script after after a restore to verify the build numbers and => s3 copies.
Revision history for this message
| Torsten Baumann (torbaumann) wrote | #1 |
| Changed in juju-ci-tools: | |
| importance: | Medium → Low |
To post a comment you must log in.
manual process step in place and understood to start at higher build numbers than we last left it.