Closed Bug 650225 Opened 10 years ago Closed 10 years ago

Move Miramar builds to the mozilla-aurora branch

Categories

(Mozilla Messaging :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: standard8)

References

Details

Attachments

(1 file)

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.
Depends on: 650227
Attached patch Buildbot changesSplinter Review
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.
Assignee: nobody → bugzilla
Status: NEW → ASSIGNED
Attachment #526286 - Flags: review?(john.hopkins)
Attachment #526286 - Flags: review?(john.hopkins) → review+
We fixed this and got it running last week.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.