731473 - Blow away elm and clone Aurora to elm

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P1)

Description

[Brian R. Bondy [:bbondy]]

What I'd like done:
-------------------

I'm done with Elm for new tasks, but I'd like someone from RelEng to blow away Elm and make it an exact copy of Aurora (including all config like confvars.sh and signing conf).  So even the channel name I'd like to match Aurora. 
I only need Windows builds as before.


What I'll be doing: 
-------------------

The only thing I want to do once I get this branch is to:
1) Push the patch from: https://bugzilla.mozilla.org/show_bug.cgi?id=731382
2) Do 1 dep build to make sure the tests are fine
3) Run 2 Nightly builds.
4) Verify the Nightly upgrade works
 
After that I'd be done with the branch and would return it.

For the dep build tests that run, I tried doing it via pushing to try but something isn't working right as you can see here for the failures unrelated to the patch:
https://tbpl.mozilla.org/?tree=Try&rev=0e9b5444d08a


If possible, high priority please:
----------------------------------

I would like to land Bug 731382 on aurora as soon as possible and also there is a test day for Aurora on March 2nd so I'd like to have this landed on Aurora and have 2 Nightly builds done on Aurora on the first of March.  

I know this pretty much just leaves Feb 29th.  Sorry for the short notice. If we can't make the test day then that is OK, but it would be nice.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

You may be able to expedite this by pulling aurora into elm, and marking the old head on default as closed (see hg ci --help). Otherwise we can get IT to reclone /releases/mozilla-aurora to /projects/elm.

I'm looking to see if we need any buildbot config or signing changes.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

I've compared the elm and mozilla-aurora buildbot-configs and the only thing we might need to do is set update_channel=aurora
  'update_channel': 'aurora',
so that we pass --enable-update-channel=aurora in the mozconfig. Currently it has 'nightly-elm' there. We use the same signing server/keys for m-c, m-a, and elm nightlies so nothing to do there AFAIK, but catlee/rail/bhearsum would know better.

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Nick Thomas [:nthomas] from comment #2)
> I've compared the elm and mozilla-aurora buildbot-configs and the only thing
> we might need to do is set update_channel=aurora
>   'update_channel': 'aurora',
> so that we pass --enable-update-channel=aurora in the mozconfig. Currently
> it has 'nightly-elm' there. We use the same signing server/keys for m-c,
> m-a, and elm nightlies so nothing to do there AFAIK, but
> catlee/rail/bhearsum would know better.

That's correct, but for Brian's purposes we might need to change the channel anyways. Brian, is it enough to have the correct keys signing the builds, or does MOZ_UPDATE_CHANNEL matter too?

Comment 4

[Brian R. Bondy [:bbondy]]

It would be best to have the same MOZ_UPDATE_CHANNEL the same just to make sure that the cert selection code works, but it's safe enough to not test that.

Comment 5

[Brian R. Bondy [:bbondy]]

Thanks for the info nthomas, I had heard about pulling from another repo and beheading the old tip but have never tried it before. I'll try now since we can just fall back to IT if I mess something up.

Comment 6

[[e-mail] (:bhearsum)]

Attachment: hardcode aurora channel

OK, let's do that then. I think we can do it in the repository rather than messing with the buildbot configs though....this patch should do it.

Comment 7

[Brian R. Bondy [:bbondy]]

So I'm going to do the update without the patch after all because I want it to check for updates and download the update from the elm branch and not for the aurora Nightlies.

Comment 8

[Brian R. Bondy [:bbondy]]

Was able to get a clone of aurora onto elm by doing these steps:
hg pull repo-to-switch-to
hg heads (shows you the new pulled in head)
hg update -r rev-to-old-tip
hg commit --close-branch
hg update -r rev-to-new-pulled-in-tip
hg push --force

This bug can be closed now, thanks everyone for your help.