Closed
Bug 584818
Opened 14 years ago
Closed 13 years ago
release clobber branch broken
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mozilla, Unassigned)
References
Details
(Whiteboard: [automation])
Nick noted that the clobberer requests for the 4.0b3build2 builds were specifying branch=nothing in their request. This means that, in clobberer, if you specify branch=mozilla-central, it doesn't actually clobber anything. Then Nick noted that we usually just specify release clobbers for an entire production master and ignore the branch or builder drop-downs. I think we should either a) remove the branch and builder drop-downs, or b) make sure the branch and builder drop-downs work (releases specify the correct branch=, and the builders/branches lists are up-to-date as of the time we resolve this bug).
Reporter | ||
Comment 1•14 years ago
|
||
(this broke the Tag builder on build 2)
Comment 2•14 years ago
|
||
Whoever fixes this has to remember to push live on build.m.o, both production and staging copies.
Updated•14 years ago
|
Priority: -- → P3
Reporter | ||
Comment 3•13 years ago
|
||
Is this still an issue?
Reporter | ||
Comment 4•13 years ago
|
||
I think we have a working clobberer.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•