1102971 - Do not trigger esr nightly builds unless there is a check-in

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

We are currently triggering an esr nightly regardless if there are any code changes.

The only reason we have esr nightly builds is for Mozmill being triggered:
https://bugzilla.mozilla.org/show_bug.cgi?id=725852#c0

I have filed bug 1102969 to switch Mozmill to listen pulse messages for per-check-in builds rarther than nightly. If bug 1102969 gets fixed there is no reason to have esr nightly builds.

Comment 1

[Armen [:armenzg]]

This is not an urgent request but it saves us resources.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

As said on IRC we cannot cope with the amount of builds for esr31 given that we have limited resources for our CI, and also have to test all the other branches, including all locales for beta and release.

I asked Armen to get a discussion thread started in the dev.automation mailing list.

Beside that please keep in mind that we do not only have nightly builds for Mozmill but also doing manual QA. Not sure how important that is those days, but please let this discussed in the thread first.

Comment 3

[Armen [:armenzg]]

This bug only is to change from 365 nightly builds a year to as many as there are days with a check-in.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This is not what you have described in comment 0:

> I have filed bug 1102969 to switch Mozmill to listen pulse messages for
> per-check-in builds rarther than nightly. If bug 1102969 gets fixed there is
> no reason to have esr nightly builds.

Here you say there is no reason to build esr nightly builds. So this was confusing. Thanks for the clarification. 

And to clarify, doing this change here is not dependent on any change on our side. Also I would kinda appreciate this change, so we only have to test esr builds when there are really code changes.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Armen, we talked about this topic today and agreed on that we can stop producing nightly builds at all in case of no-one else is using those.

What we will most likely do is to request a manual trigger of an esr nightly around 2 weeks before a release. That way we can ensure that nothing major will be broken when it comes to RC.

We hope that this will free up even more time for more important builds we have to do.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Given the above decisions and that we are under understuffed for checking those results, I have filed  https://github.com/mozilla/mozmill-ci/issues/553 for shutting down automatic ESR31 nightly builds in our CI system.

Comment 7

[Rail Aliiev [:rail]]

It sounds related to bug 1129550. We stopped generating and pushing aus2 (the old update server) snippets, but the load balancer for some reason still serves the updates of off  aus2.mozilla.org:

curl -I 'https://aus3.mozilla.org/update/3/Firefox/31.4.0esrpre/20150213000505/WINNT_x86-msvc/en-US/nightly-esr31/Windows_NT%206.1/default/default/update.xml?force=1'
HTTP/1.1 200 OK
Server: Apache
X-Backend-Server: pp-app-dist04
Cache-Control: no-store, must-revalidate, post-check=0, pre-check=0, private
Content-Type: text/xml;
Date: Sun, 15 Feb 2015 21:43:02 GMT
Transfer-Encoding: chunked
Connection: Keep-Alive
Set-Cookie: aus2a=64.228.94.154.1424036582.5216; expires=Sun, 16-Feb-2020 02:46:52 GMT; path=/; domain=aus2.mozilla.org
X-Powered-By: PHP/5.1.6
X-Cache-Info: caching

Comment 8

[Rail Aliiev [:rail]]

Ignore my last comment, it supposed to go to bug 1133250

Comment 9

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

We don't do nightly builds on esr45 since it was switched to release-promotion in bug 1253757.