1483978 - Consider adding a TC route for Android *nightly* builds on mozilla-central

Status: RESOLVED WORKSFORME

(Firefox Build System :: Task Configuration, task)

Description

[Markus Stange [:mstange]]

Here's an example Android nightly build on mozilla-central:

https://tools.taskcluster.net/groups/XoxOgsgOSOOTJsBSmZHLEQ/tasks/QCQoYvsEStO-SahYGO8RsA/details
It's only published under one TC route: tc-treeherder.v2.mozilla-central.161817e6d127e4a1fdc0ba9f041c709e09096dcb.-1

The regular, non-nightly Android builds are published under https://tools.taskcluster.net/index/gecko.v2.mozilla-central.revision.161817e6d127e4a1fdc0ba9f041c709e09096dcb.mobile

This makes them easily accessible and is used for example by Focus's build system at https://github.com/mozilla-mobile/focus-android/blob/6f7f04aeaf7141b89b0f4bc595313f3edba5bb1a/app/build.gradle#L146-L148

It would be nice to have such a route for nightly builds as well.


At the moment I'm trying to plug in a mozilla-central GeckoView build into Focus, and I've succeeded doing so but the build that was selected doesn't have symbols on the mozilla symbol server. Nightly builds do have symbols on the symbol server, so I'd like to use a nightly build here instead of a regular opt build, and the lack of TC routes is making it a bit cumbersome.

Comment 1

[Markus Stange [:mstange]]

Wait, there is https://tools.taskcluster.net/index/gecko.v2.mozilla-central.nightly.2018.08.16.latest.mobile . I wonder why that route didn't show up on the task details page.

Comment 2

[Justin Wood (:Callek)]

(In reply to Markus Stange [:mstange] from comment #1)
> Wait, there is
> https://tools.taskcluster.net/index/gecko.v2.mozilla-central.nightly.2018.08.
> 16.latest.mobile . I wonder why that route didn't show up on the task
> details page.

This doesn't show up on the task details page because that only shows routes associated with the task itself.

There is a hard limit of about 10 routes per task, due to taskcluster design limitations, to work around this - when the taskgraph is generated we "morph" the graph to remove the excess routes (leaving the one needed by treeherder) and split them off to a special task that contacts the index service directly (via API) and writes the task as belonging to the routes.

https://tools.taskcluster.net/groups/XoxOgsgOSOOTJsBSmZHLEQ/tasks/QQs5_qYLTWqrebn8tNJYzw/details is one such task, there is also https://tools.taskcluster.net/groups/XoxOgsgOSOOTJsBSmZHLEQ/tasks/aD6RtGliQ6yOjX-zr1ve9w/details 

Hope that helps.

Comment 3

[Markus Stange [:mstange]]

Yes that helps, thanks!