Closed Bug 617841 Opened 15 years ago Closed 13 years ago

set relbranch name to match BuildID

Categories

(Release Engineering :: Release Automation, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: joduinn, Unassigned)

References

Details

(Whiteboard: [cleanup][automation])

In bug#496549, we increased the relbranch name to include hours. This quick fix made it safer for us when generating two releases in the same day, so is a step in the right direction. However, once we have all release builds using the same BuildID (bug#617840), we should use that same BuildID for the relbranch name.
Priority: -- → P5
Is this just for a build 1 on a non-chemspill release ? I'm not sure what you mean to happen for build 2,3... on a relbranch, or if we re-use a relbranch for chemspill. Also note that the relbranch goes up to hours but the buildID goes to seconds.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: release → bhearsum
Hardware: x86 → All
Whiteboard: [cleanup][automation]
Given that the buildid isn't generated until (In reply to Nick Thomas [:nthomas] from comment #1) > Is this just for a build 1 on a non-chemspill release ? I'm not sure what > you mean to happen for build 2,3... on a relbranch, or if we re-use a > relbranch for chemspill. Also note that the relbranch goes up to hours but > the buildID goes to seconds. Given that we can only make this correct for build1, and the fact that buildid isn't known until well after tagging (at least, in the current implementation), I'm closing this as WONTFIX. John, if you feel strongly about this still please re-open.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.