Closed
Bug 1288182
Opened 8 years ago
Closed 8 years ago
Requesting twig repo larch be reset
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: fubar)
References
Details
Please run the script below and reset Larch to mozilla-central.
export REPO_PATH=mozilla-central
export TWIG=larch
cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
"NOTE: Coordinate with IT when this repo gets reset to push immediately without hitting the webheads. Otherwise, the permissions won't be set correctly."
We'll be wanting all CI tests, as with the normal mozilla-central tree.
* We'll be using this twig to land the localization rewrite of Firefox with l20n, and get reliable and public performance numbers.
We expect this to last 'til mid-November, or, if things go better than feared, mid-September.
This twig was previously owned by dolske, who said on #releng that they're done with it.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → klibby
Assignee | ||
Comment 1•8 years ago
|
||
larch reset. will ping #releng to prod the buildbot schedule, and taskcluster to prod their end.
> "NOTE: Coordinate with IT when this repo gets reset to push immediately without hitting the webheads. Otherwise, the permissions won't be set correctly."
I'm not sure where this comes from. By default it's set to scm_level_2; do you need it set to scm_l10n?
Flags: needinfo?(l10n)
Comment 2•8 years ago
|
||
larch pushId reset to 0 in mozilla-taskcluster.
Reporter | ||
Comment 3•8 years ago
|
||
scm_level_2 is good enough for us, thanks.
To relieve the time to push, can we update larch up to fdcee57b4e4f from mozilla-central?
Flags: needinfo?(l10n)
Assignee | ||
Comment 4•8 years ago
|
||
ok, reset it as m-c@fdcee57b4e4f and I've poked releng/taskcluster to notify their systems.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 5•8 years ago
|
||
no update needed -- pushId is still 0
You need to log in
before you can comment on or make changes to this bug.
Description
•