Confirmed users
74
edits
Mikedeboer (talk | contribs) m (table formatting) |
Mikedeboer (talk | contribs) (Updated links and removed obsolete twigs) |
||
| Line 20: | Line 20: | ||
<pre> | <pre> | ||
export REPO_PATH=[path to repo to clone from] # eg: users/lsblakk_mozilla.com/staging or comm-central | export REPO_PATH=[path to repo to clone from] # eg: users/lsblakk_mozilla.com/staging or comm-central | ||
export TWIG=[ | export TWIG=[birch|cedar|larch|maple] # whichever twig you booked | ||
cd /repo/hg/scripts/ | cd /repo/hg/scripts/ | ||
| Line 27: | Line 27: | ||
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured. | * '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured. | ||
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. (This needs to happen on both legacy buildbot & taskcluster schedulers.) If you don't see the expected builds, check with the automation teams to ensure their reset occurred. | * After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. (This needs to happen on both legacy buildbot & taskcluster schedulers.) If you don't see the expected builds, check with the automation teams to ensure their reset occurred. | ||
* Sit back and watch your builds and test results roll in (eg [ | * Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]). | ||
<div id="unbook"></div> | <div id="unbook"></div> | ||