[push-apk] release: activate rollout percentage

RESOLVED FIXED

Status

defect
P1
normal
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: jlorenzo, Assigned: jlorenzo)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(firefox55 fixed)

Details

Attachments

(3 attachments)

In bug 1317783, push-apk tasks publish fennec at 100% for mozilla-aurora, mozilla-beta and mozilla-release. We don't want a full rollout on release, though.
Priority: -- → P1
Comment on attachment 8854420 [details] [review]
pushapkscript PR

r+ with changes requested.
Attachment #8854420 - Flags: review?(aki) → review+
Comment on attachment 8855241 [details]
Bug 1353333 - [push-apk] release: activate rollout percentage

https://reviewboard.mozilla.org/r/127106/#review129974

Will we need a 2nd task to bump this to 100%?
Attachment #8855241 - Flags: review?(aki) → review+
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ba97ba73f72d
[push-apk] release: activate rollout percentage r=aki
(In reply to Aki Sasaki [:aki] from comment #5)
> Will we need a 2nd task to bump this to 100%?

I'd say not for the moment. I think it's better to have parity with Desktop release. Changing the rollout percentage is like updating a balrog rule. Therefore, it'd be better the have a human do it.

Moreover, we might want to cut the updates until the next build. This makes the workflow of the 100% task uncertain.

Finally, pushapkscript is currently not able to deal with tasks that don't have any upstream artifacts. So if we want to reach that point, that'll require some changes in:
* mozapkpublisher
* pushapkscript (and puppet)
* the taskgraph
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/59448b55c35f
[push-apk] release: activate rollout percentage r=aki
https://hg.mozilla.org/mozilla-central/rev/59448b55c35f
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Depends on: 1428444
No longer depends on: 1428444
You need to log in before you can comment on or make changes to this bug.