Closed Bug 1447688 Opened 2 years ago Closed 2 years ago

[tcmigration cleanup] retire first generation / BB mozharness scripts + configs

Categories

(Release Engineering :: Release Automation: Other, enhancement)

enhancement
Not set

Tracking

(firefox61 fixed)

RESOLVED FIXED
Tracking Status
firefox61 --- fixed

People

(Reporter: mtabara, Assigned: mtabara)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

While working on some partner repacks bits under bug 1447673 I realized we haven't killed the old code for beetmover (the first generation, the one in-tree).

It's still used in releasetasks by esr52.X but since we're not doing any migrations there and esr60 is soon due to arrive, I think it's safe to kill that code.

First things that come in mind, but not limited to are:
* script itselft[1]
* all configs [2]
* docker image [3]
* potentially others

We can make the changes on central and let them ride the trains.

[1]: https://hg.mozilla.org/mozilla-central/file/tip/testing/mozharness/scripts/release/beet_mover.py
[2]: https://hg.mozilla.org/mozilla-central/file/tip/testing/mozharness/configs/beetmover
[3]: https://hg.mozilla.org/mozilla-central/file/tip/taskcluster/docker/beet-mover
Blocks: 1442684
Renaming this bug as we can apply the same logic to multiple former mozharness scripts that are ready to be retired since we switched lots of the code to:

* TC + mozharness
* scriptworkers
Summary: [tcmigration cleanup] retire first generation of in-tree beetmover → [tcmigration cleanup] retire first generation / BB mozharness scripts + configs
Forgot of Thunderbird. Will kill only the relpro-related scripts + related configs.
Now that all releases are BB free, we can go ahead and clean a bit the tree from some useless scripts, configs and alike.
This includes:


  # beetmover along with configs, docker images and such
 # postrelease scripts which are strictly relpro related + configs

Observation:
* a note on esr52 and Thunderbird. These changes are supposed to ride the trains so they don't impact esr52 where we won't be merging any code anymore. As to Thunderbird, it's not impacted as the postrelease scripts were added to relpro releases only.
Comment on attachment 8968523 [details]
Retire first generation of in-tree beetmover and relpro postrelease scripts

Rail Aliiev [:rail] ⌚️ET has approved the revision.

https://phabricator.services.mozilla.com/D961
Attachment #8968523 - Flags: review+
Pushed by mtabara@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f5f4089f457e
Retire first generation of in-tree beetmover and relpro postrelease scripts.r=rail DONTBUILD
Followed-up with a quick fix, fixes D bustage.
@rail: does this look good? 

https://phabricator.services.mozilla.com/D961
Flags: needinfo?(mtabara) → needinfo?(rail)
r+ed!
Flags: needinfo?(rail)
Pushed by mtabara@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8710c034fb44
Retire first generation of in-tree beetmover and relpro postrelease scripts.r=rail
(In reply to Rail Aliiev [:rail] ⌚️ET from comment #8)
> r+ed!

Thanks. landed to inbound. let's see how this one goes!
https://hg.mozilla.org/mozilla-central/rev/8710c034fb44
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.