Closed
Bug 1353333
Opened 8 years ago
Closed 8 years ago
[push-apk] release: activate rollout percentage
Categories
(Release Engineering :: Release Automation: Other, defect, P1)
Release Engineering
Release Automation: Other
Tracking
(firefox55 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: jlorenzo, Assigned: jlorenzo)
References
Details
Attachments
(3 files)
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.
Updated•8 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Attachment #8854420 -
Flags: review?(aki)
Comment 2•8 years ago
|
||
Comment on attachment 8854420 [details]
pushapkscript PR
r+ with changes requested.
Attachment #8854420 -
Flags: review?(aki) → review+
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 5•8 years ago
|
||
mozreview-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
Assignee | ||
Comment 7•8 years ago
|
||
(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
Comment 8•8 years ago
|
||
Backed out for flake8 linting failure:
https://hg.mozilla.org/integration/autoland/rev/1cf1b7333d9858ce7f09d163aec78c2825a210b3
Push with failure: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=ba97ba73f72d4e8a36e9e05400b5a3056624a43e&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable
Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=89471225&repo=autoland
>TEST-UNEXPECTED-ERROR | /home/worker/checkouts/gecko/taskcluster/taskgraph/util/scriptworker.py:370:1 | expected 2 blank lines, found 1 (E302)
Flags: needinfo?(jlorenzo)
Comment hidden (mozreview-request) |
Comment 10•8 years ago
|
||
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/59448b55c35f
[push-apk] release: activate rollout percentage r=aki
Assignee | ||
Comment 11•8 years ago
|
||
Sorry about the lint issue. I fixed it in the latest patch, see: https://treeherder.mozilla.org/#/jobs?repo=try&revision=ec0dd46a0706dd5abe1618e289910734ccd0284e
It has reached autoland. In the meantime, the patch also landed on:
* https://hg.mozilla.org/releases/mozilla-aurora/rev/2cc17421d483080c72a1a2dbb9a74d97bd180773
* https://hg.mozilla.org/releases/mozilla-beta/rev/21fda0371ac39ccfffc63b703d89c9f55ad62da4
Flags: needinfo?(jlorenzo)
Comment 12•8 years ago
|
||
bugherder |
Assignee | ||
Comment 13•8 years ago
|
||
pushapkscript 0.3.1 released at https://github.com/mozilla-releng/pushapkscript/releases/tag/0.3.1
Puppet patch landed on production at https://hg.mozilla.org/build/puppet/rev/a795913bae5f1e03acde53c71fa2e7a16cd35d08
You need to log in
before you can comment on or make changes to this bug.
Description
•