[try-staging] Make bouncer check tasks work in staging releases.
Categories
(Release Engineering :: Release Automation: Bouncer, enhancement)
Tracking
(firefox67 fixed, firefox68 fixed)
People
(Reporter: tomprince, Assigned: tomprince)
References
Details
Attachments
(7 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
I beleive these entries date from when bouncer config was handled by mozharness
rather than bounerscript and are now obsolete.
Assignee | ||
Comment 3•5 years ago
|
||
Fennec doesn't have a bouncer check task, and bouncer is update via bouncerscript.
Assignee | ||
Comment 4•5 years ago
|
||
These existed for when bouncer was updated via mozharness, and they are unused in bouncer-check.
By removing the paths, we make the configuration easier to read and update.
Assignee | ||
Comment 5•5 years ago
|
||
In automation, the script is run with mach python
, and all the dependencies
are vendored, so just use them directly.
Pushed by mozilla@hocat.ca: https://hg.mozilla.org/integration/autoland/rev/1339cb993b08 [try-staging] Support bouncer-check in staging; r=aki https://hg.mozilla.org/integration/autoland/rev/0e5ad75bf07d [mozharness] Remove unused bouncer_check config entries; r=mtabara https://hg.mozilla.org/integration/autoland/rev/111aa230d41e [mozharness] Remove unused bouncer configuration for fennect; r=mtabara https://hg.mozilla.org/integration/autoland/rev/4daa02d1aa20 [mozharness] Simplify bouncer-check configuration to not include paths; r=mtabara https://hg.mozilla.org/integration/autoland/rev/310d07e69df5 Don't create fresh virtualenv for bouncer-check; r=mtabara
Assignee | ||
Comment 7•5 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/6fb4bb5bb70e
https://hg.mozilla.org/releases/mozilla-beta/rev/d99da487f0f6
https://hg.mozilla.org/releases/mozilla-beta/rev/b746cd794263
https://hg.mozilla.org/releases/mozilla-beta/rev/043e6648282f
https://hg.mozilla.org/releases/mozilla-beta/rev/52730b618189
Comment 8•5 years ago
|
||
bugherder |
Assignee | ||
Comment 9•5 years ago
|
||
The previous changes only changed the check in the release process. This also
updates the periodic check.
Assignee | ||
Comment 10•5 years ago
|
||
We only run the cron job on release branches, so it will only get scheduled
there. By not otherwise restricting the job, it makes it easier to test the
cron job on other branches (like try).
Comment 11•5 years ago
|
||
Pushed by mozilla@hocat.ca: https://hg.mozilla.org/integration/autoland/rev/e5ebda0bbbf1 [try-staging] Specify bouncer-prefix in cron bouncer check as well; r=mtabara https://hg.mozilla.org/integration/autoland/rev/26eb65cf9325 [try-staging] Don't restrict the branch that cron-bouncer-check runs on; r=mtabara
Comment 12•5 years ago
|
||
bugherder uplift |
Comment 13•5 years ago
|
||
bugherder |
Description
•