1198480 - Add comm-* repositories to orangefactor

Status: RESOLVED FIXED

(Tree Management Graveyard :: OrangeFactor, defect)

Description

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

I'd like to see if we can use orange factor for the comm-* trees. If possible, please add the following trees:

comm-central
comm-aurora
comm-beta
comm-esr38

Thanks!

Comment 1

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

This may also include adding "mozmill" to the test suites.

Comment 2

[Ed Morley [:emorley]]

Added those four repos as well as the jobtype of mozmill (which really only populates the filter UI, but for completeness), in:
https://hg.mozilla.org/automation/orangefactor/rev/380e6faae7a2

And deployed:

[[e-mail]3 orangefactor]$ hg pull -uv
pulling from http://hg.mozilla.org/automation/orangefactor/
searching for changes
all local heads known remotely
adding changesets
adding manifests
adding file changes
added 2 changesets with 4 changes to 4 files
resolving manifests
getting html/scripts/woo.utils.js
getting server/orangefactor.conf
getting woo_mailer.py
getting woo_mailer.sh
4 files updated, 0 files merged, 0 files removed, 0 files unresolved
[[e-mail]3 orangefactor]$ exit
[[e-mail]3 ~]# /etc/init.d/orangefactor stop; /etc/init.d/orangefactor start
stopping orangefactor                                      [  OK  ]
starting orangefactorspawn-fcgi: child spawned successfully: PID: 5843
                                                           [  OK  ]

eg:
http://brasstacks.mozilla.com/orangefactor/?display=OrangeFactor&endday=2015-09-01&startday=2015-08-18&tree=comm-central

The score doesn't work well when there are zero comm-central pushes in a day but yet jobs still triggered (something that doesn't really happen on other repos), but that's kinda unavoidable at the moment. OF v2 will use Treeherder's data directly, which may mean we can be smarter about this (and we may also switch to another way of calculating the score - eg per job rather than per push).

Comment 3

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Thanks for taking care, looks great!

> The score doesn't work well when there are zero comm-central pushes in a day
> but yet jobs still triggered (something that doesn't really happen on other
> repos), but that's kinda unavoidable at the moment. OF v2 will use
> Treeherder's data directly, which may mean we can be smarter about this (and
> we may also switch to another way of calculating the score - eg per job
> rather than per push).

Usually comm-* only builds when actually pushed to the comm repo. I recently retriggered a few builds though, could that be it?

Comment 4

[Ed Morley [:emorley]]

Possibly :-)