Closed Bug 1537713 Opened 11 months ago Closed 6 months ago

improve beetmover resilience by switching Thunderbird and Devedition to declarative artifacts; cleanup afterwards

Categories

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

enhancement
Not set

Tracking

(firefox71 fixed)

RESOLVED FIXED
Tracking Status
firefox71 --- fixed

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

User Story

Q3 goal: improve beetmover resilience by switching Thunderbird and Devedition to declarative artifacts; cleanup afterwards

Attachments

(5 files)

In Q1 we are undergoing changes that move the beetmover templates in-tree. This work makes beetmover more ligthweight and reduces our operations when an urgent fix is needed.

One of the long-time running problems we have been having with beetmover is our tests coverage. We often made mistakes both in-tree and in beetmoverscript that weren't caught, despite having 100% code coverage. That is because we have a dozen types of beetmover types but the tests only cover a tiny fraction of those.

This OKR should track work to improve this in order to catch potential errors early. This includes:

  • rewrite of the beetmoverscript tests following the declarative artifacts work in Q1

  • support integration tests for all types of beetmover

  • add tests coverage in-tree for templates as well

FWIW, operational tests/staging testing has taken 60% of declarative artifacts world. Mostly because there wasn't a clear way of ensuring destinations will match and automate that process verification.

Moreover, there's various weird things that beetmoverscript is consuming from a task, things like task.extra{} and task.tags{}. I'd really love for those to go away and have beetmoverscript solely rely on payload.

Integration tests should also ensure that when an in-tree manifest change happens, that doesn't or does affect the manifest.json (that's consumed by balrogworkers downstream). I had to go over that process manually.

Depends on: 1520244
User Story: (updated)
Depends on: 1567124
Blocks: 1567124
No longer depends on: 1567124
Summary: improve beetmover resilience for release pipeline stability → improve beetmover resilience by switching Thunderbird and Devedition to declarative artifacts; cleanup afterwards
See Also: → 1530728
Assignee: nobody → mtabara

Switch Devedition to declarative artifacts

Attachment #9091582 - Attachment description: Bug 1537713 - switch Devedition to declarative artifacts. → Bug 1537713 - switch Devedition to declarative artifacts. Cleanup
Attachment #9091582 - Attachment description: Bug 1537713 - switch Devedition to declarative artifacts. Cleanup → Bug 1537713 - switch Devedition to declarative artifacts.r=sfraser a=release
Pushed by mtabara@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/83d73c85529a
switch Devedition to declarative artifacts.r=sfraser a=release

Once https://hg.mozilla.org/integration/autoland/rev/83d73c85529a gets to central & beta, we can close this bug as follows:

  • Devedition + Thunderbird are now in declarative-artifacts world as well.
  • large cleanup in transforms to remove conflicting artifacts is now done
  • some initial cleanup in beetmoverscript is now completed, courtesy to the PRs enumerated in this bug.

More cleanup in beetmoverscript is tracked in bug 1567124 but it's due to happen in Q4 only because we need to wait until we EOL esr60.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED

Grafted to beta too so that tomorrow's Devedition picks it up.
https://hg.mozilla.org/releases/mozilla-beta/rev/e7f3f12d59e3b95b63bef535fa022ac9646afc9f

You need to log in before you can comment on or make changes to this bug.