Basically this file needs to be updated https://github.com/mozilla/treeherder-service/blob/master/treeherder/model/fixtures/repository.json with ideally two projects (one for pull requests / one for master)

I made some arbitrary naming decisions here. Feel free to provide guidance. I'll do the GELAM changes separatelike once we've finalized all the stuff here.

Comment on attachment 8518417 [details] Add the repository and a group A couple of comments: 1- are we gonna have multiple repositories under the "gaia app libs" group? I would set the new repository under "taskcluster" (pk=4) unless you are positive there will be more. 2- all the other gaia repositories have a codebase named "gaia", can we use it for GELAM as well?

Answering your questions first: (In reply to Mauro Doglio [:mdoglio] from comment #2) > 1- are we gonna have multiple repositories under the "gaia app libs" group? > I would set the new repository under "taskcluster" (pk=4) unless you are > positive there will be more. There are some other gaia apps with their own upstream-ish repositories like https://github.com/mozilla-b2g/caldav > 2- all the other gaia repositories have a codebase named "gaia", can we use > it for GELAM as well? gaia-email-libs-and-more lives at https://github.com/mozilla-b2g/gaia-email-libs-and-more. So it's not strictly from the gaia repo, but maybe for our purposes it works? I don't actually understand the semantics; I had looked at https://treeherder-service.readthedocs.org/en/latest/common_tasks.html#add-a-new-repository but didn't see anything; I probably should have checked the code though. The expected use-cases for all these things reporting are: - Helping protect against Gecko regressions; b2g-desktop is getting tested and the GELAM tests are doing that. There have been multiple gecko regressions recently that gecko lacked coverage for (which constitutes gecko bugs and we've added gecko coverage for), but we'd like to have test coverage. We'd probably want these run whenever a new b2g-desktop gets spun, and we'd want it to turn red. - Development of gaia-email-libs-and-more for Firefox OS / Gaia purposes: - Track the GELAM 'master' branch. This could maybe happen for free as a result of the b2g-desktop tests above? - Pull requests to GELAM. - Development of GELAM to support a desktop email app. This might entail a long-lived branch that eventually gets merged to master. It would also have pull-requests against it. - Tests run against real servers using GELAM master (and maybe the long-lived branch) to detect regressions of our handling of real-world mail server configurations that might change. In some cases these might just encounter server outages (hotmail outage, gmail outage). These would probably be run using the TaskCluster API on a daily/semi-daily basis and would not want to be something that would distract anyone developing gaia or gecko. These would be just for the email developers and maybe QA. - Maybe some upstream lib tracking. We use a bunch of lower level libraries referred to as "email.js", documented at http://emailjs.org/ and which we are trying to actively collaborate on. They currently all use travis for their tests. For all involved or just Mozilla's benefit, it could potentially be useful for them to also run on taskcluster, especially if we could then run some tests in realistic configurations like with actual web-browsers instead of phantom.js in some cases, etc. :lightsofapollo, could you weigh in on the extent to which the "gaia apps" quasi-bucket makes sense given your previous involvement in calendar, etc.

We have almost 500 open bugs, which is starting to become hard to manage. Please reopen if/when any further action is going to be taken here (ideally when the TC parts are complete and support just needs to be added to Treeherder).

We still want to do this. I'll move this to the Gaia::E-mail component if it's cluttering up the Treeherder component too much.