Closed Bug 1527206 Opened 8 months ago Closed 7 months ago

[declarative artifacts] roll out Fennec to beta and release

Categories

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

enhancement
Not set

Tracking

(firefox68 fixed)

VERIFIED FIXED
Tracking Status
firefox68 --- fixed

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

Attachments

(1 file, 1 obsolete file)

This is to track the enabling of the declarative artifacts within our release branches.

Use separate manifests per project in beetmover transform.

Attachment #9045337 - Attachment is obsolete: true
Blocks: 1529525

https://phabricator.services.mozilla.com/D20540 is ready to land on Monday, as soon as we GTB Fennec-67.0b3. We do this in order to avoid any additional disruption in first Fennec beta of the cycle.

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #3)

https://phabricator.services.mozilla.com/D20540 is ready to land on Monday, as soon as we GTB Fennec-67.0b3. We do this in order to avoid any additional disruption in first Fennec beta of the cycle.

Patch contains enabling declarative artifacts for Fennec release too.

Once we land on Monday, this will ride the trains for 67.0.

Attachment #9045389 - Attachment description: Bug 1527206 - test roll-out of declarative artifacts in Fennec beta → Bug 1527206 - roll-out declarative artifacts for Fennec beta and release
Pushed by mtabara@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fa7672715203
roll-out declarative artifacts for Fennec beta and release. r=sfraser a=release
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED

(In reply to Raul Gurzau (:RaulGurzau) from comment #6)

https://hg.mozilla.org/mozilla-central/rev/fa7672715203

Grafted to mozilla-beta - https://hg.mozilla.org/releases/mozilla-beta/rev/a1d4c53a4b80

Next Monday's 67.0b5 Fennec should pick this up and be done via declarative artifacts.

67.0b4 Fennec worked like a charm with declarative artifacts: https://tools.taskcluster.net/groups/H4aa5jnXRx6RQrNo4k4hug

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.