523995 - Update ThunderbirdTry monitoring

Status: VERIFIED FIXED

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Description

[Serge Gautherie (:sgautherie)]

1- Reconfigure it:
It should monitor (c-c) http://hg.mozilla.org/try-comm-central/,
not (m-c) http://hg.mozilla.org/try/.

2- Disable it, ftb:
as this repo. is not updated until bug 494747 is fixed.

Comment 1

[Serge Gautherie (:sgautherie)]

3- Oh!
Should c-c trees be removed from
http://tests.themasta.com/tinderboxpushlog/wrongtree.html?tree=dumb
now that they are (duplicated) at
http://build.mozillamessaging.com/tinderboxpushlog/wrongtree.html?tree=dumb
?!

Comment 2

[Philippe M. Chiasson (:gozer)]

(In reply to comment #1)
> 3- Oh!
> Should c-c trees be removed from
> http://tests.themasta.com/tinderboxpushlog/wrongtree.html?tree=dumb

I don't know exactly what is gained by that? I don't see anything wrong with having a little duplication there, especially since it's quite likely that tinderboxpushlog will be updated more regularly and having TB kept in there might help ensure it keeps on working with comm-central things.

Just my 0.02$

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> (In reply to comment #1)
> > 3- Oh!
> > Should c-c trees be removed from
> > http://tests.themasta.com/tinderboxpushlog/wrongtree.html?tree=dumb
> 
> I don't know exactly what is gained by that?

Don't wonder what the difference/usefulness of the two is.

For example, currently, only the MoMe TB3.0 has been updated to link to c-1.9.1:
MoCo TB3.0 still points to c-c.

> I don't see anything wrong with
> having a little duplication there, especially since it's quite likely that
> tinderboxpushlog will be updated more regularly and having TB kept in there
> might help ensure it keeps on working with comm-central things.

Well, I just discovered the MoMe-tbpl ... and I must say I'm still wondering why we need both (especially if duplicated)?
(Is that "documented" somewhere I could learn about?)

> Just my 0.02$

Comment 4

[Serge Gautherie (:sgautherie)]

(In reply to comment #3)
> I'm still wondering why we need both (especially if duplicated)?
> (Is that "documented" somewhere I could learn about?)

gozer, ping for answer.

Comment 5

[Philippe M. Chiasson (:gozer)]

(In reply to comment #4)
> (In reply to comment #3)
> > I'm still wondering why we need both (especially if duplicated)?
> > (Is that "documented" somewhere I could learn about?)
> 
> gozer, ping for answer.

Basically, like many other things, so we can independently run our own stuff. The defaults on our instance are Thunderbird ones and so forth. It's a branch of the moco one, and I routinely pull & merge changes back into our to keep it in sync.

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to comment #5)

Summary of our IRC discussion:

Point 1 and 2:
In http://build.mozillamessaging.com/tinderboxpushlog/Config.js,
change |"ThunderbirdTry": "try",| to |// "ThunderbirdTry": "try-comm-central/",|.

Point 3:
Yeah, I agree more with your comment 5 than I did with your comment 2.
I'll morph bug 523981 to just have MoCo TBPL stop monitoring comm-* apps.

Comment 7

[Philippe M. Chiasson (:gozer)]

(In reply to comment #6)
> (In reply to comment #5)
> 
> Summary of our IRC discussion:
> 
> Point 1 and 2:
> In http://build.mozillamessaging.com/tinderboxpushlog/Config.js,
> change |"ThunderbirdTry": "try",| to |// "ThunderbirdTry":
> "try-comm-central/",|.

Done, pushed.

Comment 8

[Serge Gautherie (:sgautherie)]

V.Fixed, per MoMe TBPL.