Closed Bug 1461668 Opened 6 years ago Closed 6 years ago

fake "new release" behavior in Ship-it v1 staging by using shipitscript and Ship-it v2 staging

Categories

(Release Engineering :: Applications: Shipit, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

Attachments

(1 file)

Forgot to file this bug, I'm working on the patches. Will add more comments in a bit.
Note to self: add comprehensive `scopes.md` for the shipitscript repo.
FWIW - this is the current PR I'm working on. Will need to tweak in-tree tasks as well.
I added the following (staging scopes for now): project:releng:ship-it:server:staging project:releng:ship-it:action:mark-as-started project:releng:ship-it:action:mark-as-shipped under moz-tree:level:3:gecko role. Not ideal but we can revisit later. [1]: https://tools.taskcluster.net/auth/scopes/project%3Areleng%3Atreescript%3Aaction%3A*/role:moz-tree%3Alevel%3A3%3Agecko
To sum-it up: * shipitscript PR is here[1] * in-tree patch is here[2] * scopes were amended in comment 4 * puppet changes are here[3] Immediate leftovers for me: * fix branch as it's now `maple` instead of `projects/maple` * fix Submtted by field as it's now `shipit-scriptworker-stage`. Or maybe not? * test Fennec and Devedition altogether. Pay attention to l10n fields too. for Firefox it worked like a charm! Future leftovers when we're ready to switch to production: * uplift in-tree changes to central/beta * land puppet changes to production and un-pin the dev worker * merge shipitscript and bump a production version * amend the production scopes as well, similarly to comment 4 but for production this time * amend the in-tree kind to make sure it only runs for mozilla-beta and is ignored for the rest (check binary transparency model maybe or use the run-on-projects field) * run a general end-to-end config diff to make sure I'm not breaking mark-as-shipped task in other projects/graphs and the existing one is looking good (mark-as-started) [1]: https://github.com/mozilla-releng/shipitscript/pull/8 [2]: https://hg.mozilla.org/projects/maple/rev/1b38998d6310b76b618d8596e6aa78ebec4f14cb [3]: https://github.com/MihaiTabara/build-puppet/tree/started
Blocks: 1466627
Summary: fake "new release" behavior in Ship-it v1 by using shipitscript and Ship-it v2 → fake "new release" behavior in Ship-it v1 staging by using shipitscript and Ship-it v2 staging
This worked like a charm in staging. More comments on leftover to roll this to production when the times comes in a few weeks, I filed 1466627.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
FTR, follow-up fix on maple to fix l10nchangesets Fennec: https://hg.mozilla.org/projects/maple/rev/48d85c1f695f180133064428dfed85c7a904c236
Blocks: 1475101
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: