645764 - Miramar builds are being triggered from mozilla-central pushes.

Status: RESOLVED WONTFIX

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Description

[Mark Banner (:standard8)]

I've been watching the Miramar tree and I've noticed that there's builds being triggered when no-one is pushing to comm-central or to mozilla-2.0.

It looks like the Miramar (comm-2.0) builds are being triggered from mozilla-central checkins.

Not sure what is going on here, but it isn't good for builder availability.

Comment 1

[John Hopkins (:jhopkins)]

Mark: can you link to an example build, please?

Comment 2

[John Hopkins (:jhopkins)]

Here is an example build (from standard8):

 https://buildbot-admin.mozillamessaging.com/production/builders/WINNT%205.2%20comm-2.0%20build/builds/97

The change that triggered the build is from the mozilla-central branch.  I did some digging through the buildbot database and found this:

 http://pastebin.mozilla.org/1195260

Notice the branch says 'comm-central', not 'mozilla-central'.  Somewhere, we're changing the branch name to comm-central and I believe that is causing the problem because the Scheduler we create is listening for comm-central changes.

Comment 3

[Mark Banner (:standard8)]

So I did look at this briefly before. I think the issue may be around the use of hg_branch in config.py, and then this code:

http://hg.mozilla.org/build/buildbot-configs/file/462585ba7d5c/thunderbird/mozillabuild.py

I think I tried changing hg_branch (to be comm-central or comm-2.0) and adding a comm_central_branch pointing to the repo we're checking out (comm-central) and then adjusting the code in mozillabuild.py.

However I couldn't quite get it to work, maybe someone else can ;-)

Comment 4

[John Hopkins (:jhopkins)]

We may want to wait until our new branching strategy is finalized before addressing this.

Comment 5

[Justin Wood (:Callek)]

For what its worth, SeaMonkey was hitting the same issue, though with different code to trigger it; I'm deferring our solution on the base issue to the symptom fix for us of branching comm-central.

I also expect this will be (short-term) wontfixed for you in favor of no longer building on m-2.0

Comment 6

[Mark Banner (:standard8)]

This is now ok with the separation of branches.