Closed
Bug 1186659
Opened 10 years ago
Closed 10 years ago
mozharness android builds are not locked to m-a
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Unassigned)
References
Details
Attachments
(1 file)
|
1.32 KB,
patch
|
bhearsum
:
review+
jlund
:
checked-in+
|
Details | Diff | Splinter Review |
I just noticed that mh android builds are not locked to m-a so they will ride the trains to beta. Which iiuc, is bad since we do not want beta per checkin android builds to use mozharness if releases use ReleaseBuildFactory (fragmenting the release vs per-checkin process)
http://hg.mozilla.org/build/buildbot-configs/file/cc8182b3d6e5/mozilla/config.py#l3141
I think should match http://hg.mozilla.org/build/buildbot-configs/file/cc8182b3d6e5/mozilla/config.py#l3135
|
Reporter | |
Comment 1•10 years ago
|
||
dump_master showed this was a no-op as expected.
Attachment #8645506 -
Flags: review?(bhearsum)
|
||
Comment 2•10 years ago
|
||
Comment on attachment 8645506 [details] [diff] [review]
150809_block_android_mh_from_uplifting_to_beta
Review of attachment 8645506 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks for catching this!
Attachment #8645506 -
Flags: review?(bhearsum) → review+
|
|
Reporter | |
Comment 3•10 years ago
|
||
Comment on attachment 8645506 [details] [diff] [review]
150809_block_android_mh_from_uplifting_to_beta
thanks
Attachment #8645506 -
Flags: checked-in+
|
|
Reporter | |
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 4•10 years ago
|
||
|
Assignee | |
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•