914640 - Enable automation to send jobs to try using existing pre-built gecko

Status: RESOLVED DUPLICATE of bug 991961

(Release Engineering :: General, defect)

Description

[cmtalbert]

Sometimes a gaia developer is trying to track down why their patch is failing on TBPL or they are trying to hunt down an intermittent orange on TBPL. In these cases, it would be nice to use an existing, pre built gecko build and run gaia commits against it in a try-like fashion. This automation will enable this to happen.

1. It will be a gaia-try repo in hg.
2. The repo will contain a json file. That's it.
3. The json file will contain pointers to the gecko build that we want to use and to the gaia commit that we want to test
4. Upon checkin to this repo, automation will pull the gecko build, (it's a b2g desktop build on linux) install it on a test slave, and schedule gaia UI and gaia unit tests against the slaves.
5. Results will report on TBPL for this repo (the repo is named gaia-try).

Because this still requires a push to hg, it would be nice to put a web-form in front of this repo where a developer simply hits the webform (the form is behind LDAP to enforce level 1 commit restrictions) puts the data in referring to the gecko build and the gaia commit and clicks the "go" button.

Clicking that go button would cause a bot to update the json file in this repo, thus triggering the automation.

Comment 1

[Jonathan Griffin (:jgriffin)]

catlee, security review has passed; it looks like this bug is next in line to enable gaia tryserver support; how much work is this?