The default bug view has changed. See this FAQ.

Please enable nightly builds on Maple

RESOLVED FIXED

Status

Release Engineering
General Automation
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: Ehsan, Assigned: Callek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
We're going to need these builds soon in order to let people experiment with service workers.  CCing Johnny and Andrew so that they can update this with more detailed priority info.
Yeah, we're not there yet (in fact, we have a build failures with opt builds ATM).  But soon we'll have more functionality and giving people builds that will update as more lands will immensely help dogfooding and feedback.
(Assignee)

Comment 2

3 years ago
adding ben and nick since we'll need to care how updates will work on these nightlies before we can enable.
Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the first Nightly completes. I'm happy to show someone how to do that.
(Assignee)

Comment 4

3 years ago
(In reply to Ben Hearsum [:bhearsum] from comment #3)
> Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the
> first Nightly completes. I'm happy to show someone how to do that.

I thought something needed to change in-tree as well...
(In reply to Justin Wood (:Callek) from comment #4)
> (In reply to Ben Hearsum [:bhearsum] from comment #3)
> > Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the
> > first Nightly completes. I'm happy to show someone how to do that.
> 
> I thought something needed to change in-tree as well...

No, that's already changed: https://mxr.mozilla.org/mozilla-central/source/browser/app/profile/firefox.js#145
(In reply to Ben Hearsum [:bhearsum] from comment #3)
> Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the
> first Nightly completes. I'm happy to show someone how to do that.

Do you mean after the first all-green build?  Also, https://aus4-admin.mozilla.org/rules.html isn't accessible for me (I'm not in an office or on the VPN).  Is that expected?  If I were to be able to access it, would it be clear to me how to add a rule in Balrog?  (Sorry, I don't know how this stuff works :)
(In reply to Andrew Overholt [:overholt] from comment #6)
> (In reply to Ben Hearsum [:bhearsum] from comment #3)
> > Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the
> > first Nightly completes. I'm happy to show someone how to do that.
> 
> Do you mean after the first all-green build?

The first job that managed to upload update metadata to Balrog - so likely the first green build.

> Also,
> https://aus4-admin.mozilla.org/rules.html isn't accessible for me (I'm not
> in an office or on the VPN).  Is that expected?  If I were to be able to
> access it, would it be clear to me how to add a rule in Balrog?  (Sorry, I
> don't know how this stuff works :)

Yeah, this is a RelEng managed system - it's expected that you don't have access. That part was meant for Callek.
(In reply to Ben Hearsum [:bhearsum] from comment #7)
> (In reply to Andrew Overholt [:overholt] from comment #6)
> > (In reply to Ben Hearsum [:bhearsum] from comment #3)
> > > Add a rule in Balrog (https://aus4-admin.mozilla.org/rules.html) after the
> > > first Nightly completes. I'm happy to show someone how to do that.
> > 
> > Do you mean after the first all-green build?
> 
> The first job that managed to upload update metadata to Balrog - so likely
> the first green build.

There have been a few green builds now.  I downloaded one yesterday and just checked and it said there are no updates available.  Is that expected or should I have been presented with one?
(Assignee)

Comment 9

3 years ago
Created attachment 8490803 [details] [diff] [review]
[configs] v1 - make maple have nightlies

So after chatting with ben and looking we need Maple to have nightlies itself, which it does not have yet, only builds.

This patch makes it do so.  Once this deploys we can then do the balrog magic. (using any random dep build will not work for these purposes)
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #8490803 - Flags: review?(bhearsum)
(Assignee)

Comment 10

3 years ago
Comment on attachment 8490803 [details] [diff] [review]
[configs] v1 - make maple have nightlies

Review of attachment 8490803 [details] [diff] [review]:
-----------------------------------------------------------------

::: mozilla/config.py
@@ +2522,5 @@
> +        # its dep signing server, which may have already been set to the global default.
> +        BRANCHES[branch]['platforms'][platform]['nightly_signing_servers'] = \
> +            branchConfig.get('nightly_signing_servers', branchConfig.get('platforms', {}).get(
> +                             platform, {}).get('nightly_signing_servers',
> +                             BRANCHES[branch]['platforms'][platform]['dep_signing_servers']))

to be clear, I'm not a fan of the formatting here, but its the best I could come up with. I'm open to *any* alternative styling you suggest, just be specific and I'll make it happen
Comment on attachment 8490803 [details] [diff] [review]
[configs] v1 - make maple have nightlies

Review of attachment 8490803 [details] [diff] [review]:
-----------------------------------------------------------------

::: mozilla/config.py
@@ +2522,5 @@
> +        # its dep signing server, which may have already been set to the global default.
> +        BRANCHES[branch]['platforms'][platform]['nightly_signing_servers'] = \
> +            branchConfig.get('nightly_signing_servers', branchConfig.get('platforms', {}).get(
> +                             platform, {}).get('nightly_signing_servers',
> +                             BRANCHES[branch]['platforms'][platform]['dep_signing_servers']))

The part that makes it tough for me to read is indentation and line breaks not mapping to any function calls. I suspect pep8ify made it this way. I don't really care that much though.
Attachment #8490803 - Flags: review?(bhearsum) → review+
(Assignee)

Comment 12

3 years ago
In production
I created the rule to enable these updates. URLs like https://aus4.mozilla.org/update/3/Firefox/15.0a1/20120519040218/WINNT_x86-msvc/en-US/nightly-maple/Windows_NT%206.1.1.0%20%28x64%29/default/default/update.xml?force=1 now receive updates.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
I just wanted to say that I verified this today (we had some bustage for a while that was preventing clean builds).  Thanks!
You need to log in before you can comment on or make changes to this bug.