Closed Bug 1623032 Opened 2 years ago Closed 2 years ago

RC-based flatpaks should push to beta channel the same way Snaps too

Categories

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

enhancement
Not set
normal

Tracking

(firefox76 fixed, firefox77 fixed)

VERIFIED FIXED
Tracking Status
firefox76 --- fixed
firefox77 --- fixed

People

(Reporter: mtabara, Assigned: jcristau)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

For snaps, we do push the release during the push phase courtesy to https://hg.mozilla.org/mozilla-central/file/tip/taskcluster/ci/release-snap-push/kind.yml#l18 while the RC we publish to the beta channel during the ship phases of RC week. I wonder whether we should do the same for flatpaks.

This bug is to track that.

Attached patch patch stubSplinter Review

:jcristau suggested we should do this patch.

Dropping it here for posterity, along with the correct observations that snap store is kind of different in that uploading the rc doesn't make it live, there's a human step afterwards, so it's fine to do it at push time.

Blocks: flatpak

This lets us avoid shipping on flathub before the actual release.

And, upload flatpaks for firefox release candidates to flathub's "beta"
channel.

Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Attachment #9142329 - Attachment description: Bug 1623032 - upload flatpak in the "ship" phase. r?mtabara → Bug 1623032 - upload flatpak in the "ship" phase, and push RCs to flathub beta. r?mtabara
See Also: → 1632584
Pushed by mtabara@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b3b81afcd829
upload flatpak in the "ship" phase, and push RCs to flathub beta. r=mtabara

Comment on attachment 9142329 [details]
Bug 1623032 - upload flatpak in the "ship" phase, and push RCs to flathub beta. r?mtabara

Beta/Release Uplift Approval Request

  • User impact if declined: flatpaks for 76 release candidates won't be available to beta users on flathub, and the 76 release will be available to stable users a day early
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Mihai and I double checked the release graph diffs a few times so I'm reasonably confident, plus the counterpart for snap in bug 1632584 has an uplift request. But this can reasonably wait for 77.
  • String changes made/needed:
Attachment #9142329 - Flags: approval-mozilla-beta?
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

Comment on attachment 9142329 [details]
Bug 1623032 - upload flatpak in the "ship" phase, and push RCs to flathub beta. r?mtabara

Tweak the timing of uploading Flatpak builds a bit to match what was done for Snap builds. Approved for 76.0rc1.

Attachment #9142329 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Forgot to mention, this worked like a charm in RC week - https://firefox-ci-tc.services.mozilla.com/tasks/LNbatA7CTR-euNmwquUMCw#artifacts
Thanks again :jcristau for this! \o/

Status: RESOLVED → VERIFIED
Component: Release Automation: Flatpak → Release Automation: Other
See Also: → 1659682
You need to log in before you can comment on or make changes to this bug.