1080354 - Reset Alder build configs to normal twig.

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Justin Dolske [:Dolske]]

I need a temporary project branch (1 month), but everything on https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches is currently booked. Can we create some extra slots?

(If so and it can save a step, I'll be wanting mine to be a fresh clone of https://hg.mozilla.org/releases/mozilla-release/)

Comment 1

[Hal Wine [:hwine] use NI!]

(In reply to Justin Dolske [:Dolske] from comment #0)
> I need a temporary project branch (1 month), but everything on
> https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches is
> currently booked. Can we create some extra slots?

No fresh slots are available due to load on the build system.

Your best bet is to negotiate with others who have a branch. We'll send out a "nag" email to current holders, but twigs are a user managed resource.

> (If so and it can save a step, I'll be wanting mine to be a fresh clone of
> https://hg.mozilla.org/releases/mozilla-release/)

Actually, Developer Services handles that part of the request. Please use the link in the wiki page for fastest service.

Comment 2

[Hal Wine [:hwine] use NI!]

Alder doesn't seem very active -- no commit since 2014-06-03
  http://hg.mozilla.org/projects/alder/tip/

I've added you as next in line, & ni :jcranmer here

:jcranmer -- are you done with alder?

Comment 3

[Joshua Cranmer [:jcranmer]]

I've said this more than once over email.

I'm not particularly using alder at the moment. However, it has a fair amount of non-normal build config due to it being used for TB work instead of FF. So it's probably not the best to reclaim if another is available (although it doesn't sound like there is).

Comment 4

[Hal Wine [:hwine] use NI!]

Morphing this into a request to reset the build configs on alder to standard twig configuration. (Was comm central)

:dolske - you still need to file the request to get the twit reset, and update the wiki page

Comment 5

[Justin Dolske [:Dolske]]

Ok, filed bug 1083212 and updated the wiki.

Comment 6

[Hal Wine [:hwine] use NI!]

:dolske - can you clarify what type of builds you're looking for? seeing you reset to m-r, there are differences in m-r & m-c builds that may, or may not, impact you.

Comment 7

[cmtalbert]

:hwine and :dolske:

My plan for testing here is to open this to internal folks for daily use, so it would be helpful to have nightly builds w/updates from alder if that is possible. If we can't stand that up by friday (i.e. this week) then we could back off of that.

Further, I'd like to do a first build on alder with no changes - in other words - a duplicate of the 33 release build. That way we can start with a known state.

From there, i'd like to land things as quickly as possible to enable us to get a jump on looking at these builds.

Comment 8

[Justin Dolske [:Dolske]]

(In reply to Hal Wine [:hwine] (use needinfo) from comment #6)
> :dolske - can you clarify what type of builds you're looking for? seeing you
> reset to m-r, there are differences in m-r & m-c builds that may, or may
> not, impact you.

There's a special upcoming Firefox release (bug 1073292), so we want to have a project repo where we can preland and test the ~dozen patches involved before they actually land into mozilla-central (yes, release-drivers are aware of this :).

I don't _think_ any of the changes are conditional on it it being a bona-fide Firefox release build. But if we can easily adjust the build config to make it more accurately reflect a release build, that seems worthwhile. I don't think that needs any heroic measures though (eg, things like crash reporting, signed builds, Google API keys, etc.).

I suppose updates are smart too (iirc that's been simple to enable for project branches before), but I'm not expecting there to be many additional landings, since the relevant code is already on Nightly through Beta.

Comment 9

[Hal Wine [:hwine] use NI!]

(In reply to Clint Talbert ( :ctalbert ) from comment #7)
> :hwine and :dolske:
> 
> Further, I'd like to do a first build on alder with no changes - in other
> words - a duplicate of the 33 release build. That way we can start with a
> known state.
> 
> From there, i'd like to land things as quickly as possible to enable us to
> get a jump on looking at these builds.

The config changes happened in bug 1083853, so first nightly will be available Friday morning. What that contains depends on when :dolske lands :)

Comment 10

[Justin Wood (:Callek)]

followup with r=coop over IRC https://hg.mozilla.org/build/buildbot-configs/rev/0d7b2e025dc6

Comment 11

[Justin Wood (:Callek)]

In production: 2014-10-16 19:51 PT 
(See https://wiki.mozilla.org/ReleaseEngineering:Maintenance)

Comment 12

[Justin Dolske [:Dolske]]

This was done, and in fact we're done with Alder now.