Closed Bug 1914410 Opened 2 months ago Closed 1 month ago

upload fenix/focus to candidates directory on release promotion

Categories

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

enhancement

Tracking

(firefox131 fixed)

RESOLVED FIXED
Tracking Status
firefox131 --- fixed

People

(Reporter: jcristau, Assigned: jcristau)

Details

Attachments

(2 files)

Currently fenix/focus apks and bundles are uploaded directly to the releases directory in the ship phase; instead they should match desktop: upload to candidates during the promote phase, and copy to releases on push.

Ryan, would it be ok to have fenix/focus show up in the releases directory during the push phase, as with desktop, or should we preserve the current behavior (i.e. run this during ship)?

Flags: needinfo?(ryanvm)

Change beetmover-android-app to upload to pub/{fenix,focus}/candidates/ and run
during the promote release phase; add push-to-releases tasks for fenix and
focus, that run in the push phase.

(In reply to Julien Cristau [:jcristau] from comment #2)

Ryan, would it be ok to have fenix/focus show up in the releases directory during the push phase, as with desktop, or should we preserve the current behavior (i.e. run this during ship)?

The issue is that we run the push phase for Android much earlier than we do for Desktop so we can start the 5% RC week rollout. If we had to respin the RCs, wouldn't we have to purge the releases directory then?

Flags: needinfo?(ryanvm)

Oh, right, I forgot. I'll update the patch to run android push-to-release on ship then. Thanks!

Pushed by jcristau@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d1efa409c5cb publish fenix/focus to candidates dir during release promotion. r=releng-reviewers,gbrown
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: