Closed
Bug 1213317
Opened 9 years ago
Closed 9 years ago
Move release promotion buildbot builders to separate module
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: jlund)
References
Details
Attachments
(2 files, 1 obsolete file)
5.51 KB,
patch
|
rail
:
review+
jlund
:
checked-in+
|
Details | Diff | Splinter Review |
4.49 KB,
patch
|
rail
:
review+
jlund
:
checked-in+
|
Details | Diff | Splinter Review |
It would be great to group all release promotion related builders in a single file module, that can be used from misc.py. http://hg.mozilla.org/build/buildbotcustom/file/ec6cd658f788/misc.py#l3327 is the current entry point.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jlund
Comment 1•9 years ago
|
||
I think this is a good idea. Originally it went into misc.py because it gave easy access to ci-style objects, since that's what promotion is closer too. I have a vague memory of some sort of circular import problem which that avoided too.
Assignee | ||
Comment 2•9 years ago
|
||
though not a necessary bug, I took this first as a way to familiarize myself with the buildbot code for build promotion.
this patch:
1) renames generateReleasePromotionObjects to generateReleasePromotionBuilders since we are only creating builder objects and letting bbb schedule/trigger release promotion jobs
2) moves generateReleasePromotionBuilders from misc.py to process/release.py
2) method impl now only returns a list of builders and not a dict of objects and also returns immediately if not a 'release promotion branch' (will make more sense with upcoming buildbot-configs patch
Attachment #8675342 -
Flags: review?(rail)
Assignee | ||
Comment 3•9 years ago
|
||
this patch:
1) rather than calling generateReleasePromotionBuilders from within generateReleaseBranchObjects(), we give release promotion builders their own entry call within master.cfg.
2) since generateReleasePromotionBuilders only tracks new builders, this should only be needed for the production build master.cfg (mozilla/builder_master.cfg) and the staging universal master
a dump master diff yielded a no-op for me locally. hopefully production agrees with that :)
Attachment #8675343 -
Flags: review?(rail)
Assignee | ||
Comment 4•9 years ago
|
||
same as before but removes old unused var (releasePromotionBuilders) from earlier WIP
interdiff fwiw: http://people.mozilla.org/~jlund/151017_1213317_bbot-cfgs-interdiff.patch
Attachment #8675343 -
Attachment is obsolete: true
Attachment #8675343 -
Flags: review?(rail)
Attachment #8675345 -
Flags: review?(rail)
Reporter | ||
Updated•9 years ago
|
Attachment #8675342 -
Flags: review?(rail) → review+
Reporter | ||
Updated•9 years ago
|
Attachment #8675345 -
Flags: review?(rail) → review+
Reporter | ||
Comment 5•9 years ago
|
||
Hmm, for some reason it doesn't pass check-masters.sh in my environment.
Reporter | ||
Comment 6•9 years ago
|
||
"my environment" was key here, disregard.
Assignee | ||
Comment 7•9 years ago
|
||
Comment on attachment 8675342 [details] [diff] [review]
151017_1213317_give_promotion_logic_its_own_method_entry-buildbotcustom.patch
thanks https://hg.mozilla.org/build/buildbotcustom/rev/c91ff584f674
Attachment #8675342 -
Flags: checked-in+
Assignee | ||
Comment 8•9 years ago
|
||
Comment on attachment 8675345 [details] [diff] [review]
151017_1213317_give_promotion_logic_its_own_method_entry-buildbot-configs2.patch
https://hg.mozilla.org/build/buildbot-configs/rev/3fd8f683b28d
Attachment #8675345 -
Flags: checked-in+
Reporter | ||
Comment 9•9 years ago
|
||
I think we can close this bug
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•