ReleaseEngineering/DisposableProjectRepositories: Difference between revisions

ReleaseEngineering/DisposableProjectRepositories (view source)

129 bytes removed , 15 February 2017

Update post twig reset reset scheduler notifications.

Confirmed users

1,364

edits

@@ Line 25: / Line 25: @@
 ./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
 </pre>
-* '''NOTE''': Coordinate with IT when this repo gets reset to push immediately without hitting the webheads. Otherwise, the permissions won't be set correctly.
 * '''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.
 * Sit back and watch your builds and test results roll in (eg [http://tbpl.mozilla.org/?tree=Alder Alder], [http://tbpl.mozilla.org/?tree=Birch Birch], [http://tbpl.mozilla.org/?tree=Cedar Cedar],[http://tbpl.mozilla.org/?tree=Holly Holly], [http://tbpl.mozilla.org/?tree=Larch Larch], [http://tbpl.mozilla.org/?tree=Maple Maple]).
-* '''Special note:''' the first push to your newly cloned repo may not trigger builds if the repo had been pushed to previously, which is {{bug|774862}}. If it does not, please re-open the bug and move it to Release Engineering :: General Automation with a comment 'Please reconfigure the build scheduler'.
 <div id="unbook"></div>