Closed
Bug 1269540
Opened 8 years ago
Closed 8 years ago
mozilla-release desktop builds reverted to running buildbot factories
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
1.37 KB,
patch
|
mozilla
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Which blocks doing a 46.0.1 release.
Assignee | ||
Comment 1•8 years ago
|
||
Now that we have release promotion on mozilla-release we're using mozharness for desktop builds for 46.0 and higher. ESR45/38 are still on buildbot factories (for now, I hear). This logic needed adjusting at the last merge. For the week after we merged to m-r we had version 46.0 on m-b and m-r, so we had mozharness builds on m-r. When the m-b version incremented to 47.0 (after merge from m-a) we swapped back to buildbot factories.
Attachment #8748010 -
Flags: review?(aki)
Comment 2•8 years ago
|
||
Comment on attachment 8748010 [details] [diff] [review] [buildbot-configs] mozharness for 46.0+ Review of attachment 8748010 [details] [diff] [review]: ----------------------------------------------------------------- lgtm
Attachment #8748010 -
Flags: review?(aki) → review+
Assignee | ||
Comment 3•8 years ago
|
||
Comment on attachment 8748010 [details] [diff] [review] [buildbot-configs] mozharness for 46.0+ https://hg.mozilla.org/build/buildbot-configs/rev/b21377d549ae https://hg.mozilla.org/build/buildbot-configs/rev/28a060096a22 Reconfig complete.
Attachment #8748010 -
Flags: checked-in+
Assignee | ||
Comment 4•8 years ago
|
||
Pushed a comment change to get new builds https://hg.mozilla.org/releases/mozilla-release/rev/0b8492c110be Verified we've got mozharness builds running there.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 5•8 years ago
|
||
haha, thanks for this. probably my bad locking it to a specific gecko version
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•