Closed Bug 1599128 Opened 6 years ago Closed 6 years ago

Make Fenix staging releases better configured

Categories

(Release Engineering :: Release Automation, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jlorenzo, Assigned: jlorenzo)

References

(Blocks 1 open bug)

Details

Attachments

(10 files, 2 obsolete 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
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review

Regressions caused by both bug 1582366 and bug 1595501 showed a thing: Our staging releases for mobile projects are weak. I used them when I did the taskgraph migration (bug 1580778), but I hacked my way around for sake of timing. I did a lot of configuration manuallly and it went away with bug 1595501.

Let's make staging releases better to use and migrate.

Depends on: 1597962
Attachment #9111956 - Attachment description: Bug 1599128 - part 1: Merge `mobile-pushapk-stage-phase` and `mobile-pushapk-phase` into 1 r=tomprince → Bug 1599128 - part 1: Remove unused `cron:nightly-staging` roles and merge `mobile-pushapk-stage-phase` and `mobile-pushapk-phase` into 1 r=tomprince
Attachment #9111958 - Attachment description: Bug 1599128 - part 3: Run raptor on any branch since it's already allowed on PRs r=tomprince → Bug 1599128 - part 2: Run raptor on any branch since it's already allowed on PRs r=tomprince
Attachment #9111959 - Attachment description: Bug 1599128 - part 4: Map `project:mobile:` scopes to {trust_project} instead of {alias} r=tomprince → Bug 1599128 - part 3: Map `project:mobile:` scopes to {trust_project} instead of {alias} r=tomprince
Attachment #9111961 - Attachment description: Bug 1599128 - part 5: Factorize code-coverage tokens in a dedicated feature r=tomprince → Bug 1599128 - part 4: Factorize code-coverage tokens in a dedicated feature r=tomprince
Attachment #9111962 - Attachment description: Bug 1599128 - part 6: Do not email people on forks r=tomprince → Bug 1599128 - part 5: Do not email people on forks r=tomprince
Attachment #9111963 - Attachment description: Bug 1599128 - part 7: Enable jlorenzo's Fenix fork r=tomprince → Bug 1599128 - part 6: Enable jlorenzo's Fenix fork r=tomprince
Attachment #9111957 - Attachment is obsolete: true
Blocks: 1601606
Blocks: 1601687
Blocks: 1601928

Depends on D55453

Attachment #9114125 - Attachment description: Bug 1599128 - part 8: Add mobile action → Bug 1599128 - part 8: Add mobile action r=tomprince
Attachment #9111977 - Attachment description: Bug 1599128 - part 2: Do not generate general cron job nor send email on forks r=tomprince → Bug 1599128 - part 2: Do not send email on forks r=tomprince

We're now in a better state with these patches landed and deployed. There are some improvements we can do (like Blocks: bug 1601606, bug 1601687, bug 1601928). Let's track them there.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Blocks: 1602861
Attachment #9111272 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: