Closed Bug 907941 Opened 8 years ago Closed 8 years ago
.json automatically when the gaia-ui-tests repo changes
This bug will be used to track automatic updates performed by the "gaia-ui-tests-pushbot" (see bug 907240), which update the gaia-ui-tests.json file in gaia automatically when the gaia-ui-tests repo changes.
Whenever the repo https://github.com/mozilla/gaia-ui-tests is updated, the gaia-ui-tests-pushbot will automatically update the file tests/python/gaia-ui-tests.json in the gaia repo, like so: https://github.com/mozilla-b2g/gaia/commit/8ae14172afc40e6c9be8f47b927eb998279208c9 This, in turn, will cause a gaia-pushbot update in TBPL, like so: https://hg.mozilla.org/integration/b2g-inbound/rev/35db67270042 If a commit to gaia-ui-tests causes breakage in TBPL, the sheriff should backout the corresponding gaia commit as usual, which will reset the gaia-ui-tests.json pointer to its previous state. If the commit message of this backout contains either the words "back" or "revert" (case-insensitive), the gaia-ui-tests-pushbot will stop automatic operation; it will resume after a manual commit which doesn't include either of those strings. This is necessary since otherwise the next commit to gaia-ui-tests would trigger the gaia-ui-tests-pushbot to again update gaia-ui-tests.json, likely re-breaking the tests in TBPL.
See https://intranet.mozilla.org/Auto-tools/B2G_Automation#gaia-ui-tests-pushbot for details about where the pushbot is hosted.
Seems to be working well.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
https://hg.mozilla.org/mozilla-central/rev/66870fbe0a8e https://hg.mozilla.org/mozilla-central/rev/e6cad4679624 https://hg.mozilla.org/mozilla-central/rev/f551128d430c https://hg.mozilla.org/mozilla-central/rev/6c6bf65089b6 https://hg.mozilla.org/mozilla-central/rev/ff2e4d8cb650 https://hg.mozilla.org/mozilla-central/rev/13ae92616a18 https://hg.mozilla.org/mozilla-central/rev/bc5a5f9e9f2a
(In reply to Wes Kocher (:KWierso) from comment #4) We really need to teach mcMerge to ignore anything from the pushbot(s).
You need to log in before you can comment on or make changes to this bug.