Confirm
210
edits
Changes
Made sunset of TC infrastructure more explicit
Workers are meant to start tasks once pre-requisites are met. In our specific case, we have 3 instance of [https://github.com/taskcluster/docker-worker the same worker]: one for each number of SIMs (1, 2 and 0). These workers regularly poll the testdroid reverse proxy to know how many devices are available. Once 1 is, the test task is awaken. This task will communicate through [https://github.com/taskcluster/testdroid-proxy the proxy] which is meant to centralize the authentication to bitbar's service. Hence, no task has knowledge of the credentials used. It uses the [https://github.com/mozilla-b2g/testdroid-client JavaScript client]. This client has the same responsibilities as the Jenkins plugin (find a device available, flash it, wait until flash is done).
Like above, the test task talks to a device thanks to forwarded ADB/Marionette ports. Once the task is done, it reports to Treeherder, [https://treeherder.allizom.org/#/jobs?repo=b2g-inbound&filter-job_group_symbol=e2e-py under these jobs]. As you may notice, these jobs are only visible on the stage instance of Treeherder and running against b2g-inbound. The main explanation is that the jobs were still failing highly failing intermittently. We were working on making them stable, but this project has been sunset. See For reference, see [https://bugzilla.mozilla.org/show_bug.cgi?id=1225457 bug 1225457] for the work listed to make them stablesee what was planned.
