1541122 - [try-staging] Make bouncer check tasks work in staging releases.

Status: RESOLVED FIXED

(Release Engineering :: Release Automation, enhancement)

Comment 1

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [try-staging] Support bouncer-check in staging; r?aki

Comment 2

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [mozharness] Remove unused bouncer_check config entries; r?mtabara

I beleive these entries date from when bouncer config was handled by mozharness
rather than bounerscript and are now obsolete.

Comment 3

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [mozharness] Remove unused bouncer configuration for fennect; r?mtabara

Fennec doesn't have a bouncer check task, and bouncer is update via bouncerscript.

Comment 4

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [mozharness] Simplify bouncer-check configuration to not include paths; r?mtabara

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.

Comment 5

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: Don't create fresh virtualenv for bouncer-check; r?mtabara

In automation, the script is run with mach python, and all the dependencies
are vendored, so just use them directly.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
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

Comment 7

[Tom Prince [:tomprince]]

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

[Andrei Ciure[:aciure]]

https://hg.mozilla.org/mozilla-central/rev/1339cb993b08
https://hg.mozilla.org/mozilla-central/rev/0e5ad75bf07d
https://hg.mozilla.org/mozilla-central/rev/111aa230d41e
https://hg.mozilla.org/mozilla-central/rev/4daa02d1aa20
https://hg.mozilla.org/mozilla-central/rev/310d07e69df5

Comment 9

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [try-staging] Specify bouncer-prefix in cron bouncer check as well; r?mtabara

The previous changes only changed the check in the release process. This also
updates the periodic check.

Comment 10

[Tom Prince [:tomprince]]

Attachment: Bug 1541122: [try-staging] Don't restrict the branch that cron-bouncer-check runs on; r?mtabara

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

[Pulsebot]

Pushed by [e-mail]:
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

[Daniel Varga [:dvarga]]

https://hg.mozilla.org/releases/mozilla-beta/rev/1c729b2f5e3e
https://hg.mozilla.org/releases/mozilla-beta/rev/8d526e3036bf

Comment 13

[Stefan Hindli [:stefan_hindli]]

https://hg.mozilla.org/mozilla-central/rev/e5ebda0bbbf1
https://hg.mozilla.org/mozilla-central/rev/26eb65cf9325