Closed
Bug 650225
Opened 14 years ago
Closed 14 years ago
Move Miramar builds to the mozilla-aurora branch
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
References
Details
Attachments
(1 file)
|
6.76 KB,
patch
|
jhopkins
:
review+
|
Details | Diff | Splinter Review |
Currently our Miramar builds are coming off the mozilla-2.0 branch, as we've decided to ship off of Firefox 5, we need to be get ourselves onto gecko 5.0.
As a temporary solution whilst we are working out the more specific branch details, I want to build off of mozilla-aurora so that we're working off of something that is closer to what we're going to end up with.
What I would like us to do in buildbot is:
- Rename the comm-2.0 branch to comm-aurora
- Change comm-aurora to pull the mozilla repo from http://hg.mozilla.org/mozilla-aurora/
- Change comm-aurora to pull the l10n repos from http://hg.mozilla.org/releases/l10n/mozilla-aurora
- Upload builds to comm-aurora on ftp.
I suspect we'll need to update aus to handle the comm-aurora branch as well.
| Assignee | ||
Comment 1•14 years ago
|
||
Ok, I had my head around roughly what needed doing to buildbot, so I've done what should be the config change.
We should be able to land this with a shutdown and re-start of buildbot. For production, we need to land the build config change from bug 650227 just after we restart buildbot.
Updated•14 years ago
|
Attachment #526286 -
Flags: review?(john.hopkins) → review+
| Assignee | ||
Comment 2•14 years ago
|
||
We fixed this and got it running last week.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•