migrate l10n bumper to treescript
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(firefox-esr6872+ fixed, firefox72 fixed)
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
Attachments
(5 files)
|
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr68+
|
Details | Review |
|
62 bytes,
text/x-github-pull-request
|
Details | Review | |
|
55 bytes,
text/x-github-pull-request
|
Details | Review | |
|
62 bytes,
text/x-github-pull-request
|
Details | Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review |
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
https://firefoxci.taskcluster-artifacts.net/Qy9g939aT-2YnIbh1lhdRQ/0/public/logs/live_backing.log seems to show I need to fix the purge call (or the mercurial extensions/deps).
| Assignee | ||
Comment 5•6 years ago
|
||
sheehan 12:30
@aki: I haven't seen that before but I took a look and I think it's a bug in robustcheckout
purge used to import util when that line was introduced, now imports scmutil and cmdutil instead
Updated•6 years ago
|
| Assignee | ||
Comment 7•6 years ago
|
||
Followup scriptworker-scripts PR: https://github.com/mozilla-releng/scriptworker-scripts/pull/77
| Assignee | ||
Comment 8•6 years ago
|
||
Comment 9•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Backed out changeset 11f48aaae955 (bug 1481916) for causing l10 bumper exceptions
Comment 12•6 years ago
|
||
Updated•6 years ago
|
| Assignee | ||
Comment 13•6 years ago
|
||
In https://treeherder.mozilla.org/#/jobs?repo=try&revision=f31831e913874e69cda1143b1853753ef7341437&selectedJob=277493566 , we appear to not end up in an esr68 head. https://firefoxci.taskcluster-artifacts.net/fotQEh4WSde367cteULElA/0/public/logs/live_backing.log
We could try landing and fixing if it's a problem on esr68 itself, since I don't think we'll push the wrong thing anymore. Alternately, we could block uplifting on https://github.com/mozilla-releng/scriptworker-scripts/issues/88 .
The beta-esque try push looks good after I fixed the release-type -> release_type issue. https://treeherder.mozilla.org/#/jobs?repo=try&revision=7750c5d0e8168d08244646d5fc3a05cf4dd94be6&selectedJob=277489964 and https://firefoxci.taskcluster-artifacts.net/cvCDoob-RmG8aU3vDHMs8g/0/public/logs/live_backing.log
Comment 15•6 years ago
|
||
I think if you hacked taskgraph to generate a metadata that pointed at esr68, it would test what you want.
| Assignee | ||
Comment 16•6 years ago
|
||
| Assignee | ||
Comment 17•6 years ago
|
||
The metadata hack didn't work: it broke CoT.
I:
- created a PR to add source_repo and target_repo support, and populated
source_repoin-tree - fixed the esr68 l10n dashboard link
- removed the use of
pushscopes, so we can try to push to try in the future - fixed flake8
- tested a bunch
I'm pretty confident in this now. Thanks for your help!
I was wondering if we would need a way to override ignore-closed-tree and force the cron hook, so mergeduty can run l10n-bumper. Then I realized that in the near future, we'll be kicking off both Firefox and Devedition b1 without a week of beta closure, so we may not need to force it (we just need to reopen beta to approval-only after merging, then wait for the l10n bumper to run before gtb).
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 20•6 years ago
|
||
Comment on attachment 9108892 [details]
Bug 1481916 - add l10n-bumper task. r=Callek
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: This will enable the l10n bumper for Fennec releases on esr68.
- User impact if declined: When we turn off buildbot-master01, where the retiring l10n bumper has been running, we'll no longer pick up new Fennec locale bumps. If we no longer need Fennec releases off esr68, this may be the desirable outcome.
- Fix Landed on Version: 72
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): I've tested quite a bit on Try. We now count the number of outgoing changes and make sure they match the expected number of outgoing patches.
- String or UUID changes made by this patch:
Comment 21•6 years ago
|
||
(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #20)
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: This will enable the l10n bumper for Fennec releases on esr68.
- User impact if declined: When we turn off buildbot-master01, where the retiring l10n bumper has been running, we'll no longer pick up new Fennec locale bumps. If we no longer need Fennec releases off esr68, this may be the desirable outcome.
From an l10n POV, I'd prefer to be on the safe side and continue to ship string updates on Fennec. Well, I consider this landing to the safe side than not landing it.
| Assignee | ||
Comment 22•6 years ago
|
||
Comment 23•6 years ago
|
||
Worked like a charm on beta earleir today as part of mergeduty! \o/
| Assignee | ||
Comment 24•6 years ago
|
||
:jcristau, do you have an opinion about whether we should keep running l10n bumper on esr68 for Fennec? We're going to shut down the instance that's running l10n bumper soon, and we'll need to uplift https://bugzilla.mozilla.org/attachment.cgi?id=9108892 to keep running l10n bumper on esr68.
Comment 25•6 years ago
|
||
Sounds like we should uplift then. I suspect the EOL for fennec on esr68 is a few months away still.
flod fyi.
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
Comment 26•6 years ago
|
||
| bugherder uplift | ||
Comment 27•6 years ago
|
||
Comment on attachment 9108892 [details]
Bug 1481916 - add l10n-bumper task. r=Callek
For posterity.
Comment 28•6 years ago
|
||
Every time the L10n bumper script runs, 15 lint and source test tasks are getting executed, e.g. https://firefox-ci-tc.services.mozilla.com/tasks/groups/bmNZADS2QQO30c6j8Y5Tqw
This looks like this: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&selectedJob=280274456&searchStr=python&revision=053b0bb00fedc42ea54e7a6b8e32843d7d6b7849
It made bug 1500321 more visible. Aki, does this need a follow-up action?
Updated•1 year ago
|
Description
•