Closed
Bug 727489
Opened 13 years ago
Closed 13 years ago
Use branch set to sourceRepoInfo['path'] for release AggregatingSchedulers
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: rail)
Details
(Whiteboard: [releases][automation])
Attachments
(1 file)
|
(deleted),
patch
|
bhearsum
:
review+
bhearsum
:
feedback+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
I think that all AggregatingSchedulers used in release.py should use branch set to sourceRepoInfo['path'], so the downstream builders clobber using a proper branch.
To be tested in staging.
Attachment #597446 -
Flags: feedback?(bhearsum)
|
||
Comment 1•13 years ago
|
||
Comment on attachment 597446 [details] [diff] [review]
use sourceRepoInfo['path']
If this ends up landing can you make sure to clean up the excess branches on clobberer?
Attachment #597446 -
Flags: feedback?(bhearsum) → feedback+
|
Assignee | |
Comment 2•13 years ago
|
||
Comment on attachment 597446 [details] [diff] [review]
use sourceRepoInfo['path']
This change is important for ScriptFactory based factories, since MozillaBuildFactory sets branch itself unless you pass branchName to it. Minimal staging testing done.
Attachment #597446 -
Flags: review?(bhearsum)
|
|
||
Updated•13 years ago
|
Attachment #597446 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Comment 3•13 years ago
|
||
Comment on attachment 597446 [details] [diff] [review]
use sourceRepoInfo['path']
http://hg.mozilla.org/build/buildbotcustom/rev/8fa5990e6b8c
Attachment #597446 -
Flags: checked-in+
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
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
•