907240 - Need a gaia-ui-tests pushbot

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Jonathan Griffin (:jgriffin)]

We need to make gaia-ui-tests pushbot ala the exiting gaia pushbot, which will rev the gaia-ui-tests.json file in the gaia repo whenever the hg mirror of gaia-ui-tests repo changes.

We've had two bustages of gaia-ui-tests in TBPL in the past two weeks, both caused by gaia-ui-tests getting out-of-date.  I think having an automatic pushbot is the only solution compatible with our existing infrastructure that can resolve this.

See the most recent at https://github.com/mozilla/gaia-ui-tests/issues/1262

The only difference between this and the gaia pushbot is that this will have to commit to github and not hg, since the canonical gaia-ui-tests.json file is in gaia.

Comment 1

[Aki Sasaki (not active)]

How urgent is this?

The github vs hg issue will require:

* a changed process for pull/commit/push
** the push needs extra checks to make sure we land on tip of master, not an unnamed branch
* some way to commit to github
** i don't think there's an ffxbld account with write access to gaia currently.
** we want to avoid using a human's account, because the process will break should they leave
** i'm not sure how long our internal machines will continue to have direct network access to github, given bug 617414.

Comment 2

[Jonathan Griffin (:jgriffin)]

I think we can't unhide the gaia-ui-tests until this is done.

If it's not easy to do within the rel-eng infrastructure, I think I could set up a Jenkins job to do this; commits would be made by the 'b2gautomation' user.

Comment 3

[Ed Morley [:emorley]]

Note the hg compatibility changes would help with bug 899969 too.

Comment 4

[Jonathan Griffin (:jgriffin)]

I am going to take this, and set this up on the B2G Jenkins master.  Longer-term, we can move into rel-eng infrastructure if and when appropriate.

Comment 5

[Jonathan Griffin (:jgriffin)]

I've stood up a simple pushbot on Jenkins, see bug 907941 for details.  It's currently operational; we'll leave it on for a few days and see if it causes any problems, if not, we're probably be safe to unhide the gaia-ui-tests in TBPL.