ReleaseEngineering/DisposableProjectRepositories: Difference between revisions

Jump to navigation Jump to search

ReleaseEngineering/DisposableProjectRepositories (view source)

Revision as of 15:51, 8 January 2019

324 bytes removed ,  8 January 2019
Reference correct script to reset project repo
(Updated links and removed obsolete twigs)
(Reference correct script to reset project repo)
Line 17: Line 17:


* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url}&cc=buildduty@releng.bugs request] (example: {{bug|951811}}) to IT to reset the repo for you as a clone from your own project repo (or default mozilla-central:tip). '''Copy the script below into bug request, replacing the REPO_PATH and TWIG with your repo and booked branch'''.
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url}&cc=buildduty@releng.bugs request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
<pre>
export REPO_PATH=[path to repo to clone from]                # eg: users/lsblakk_mozilla.com/staging or comm-central
export TWIG=[birch|cedar|larch|maple]    # whichever twig you booked
 
cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
</pre>
* '''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. 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 [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]).   
* 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]).   


Sheehan
33

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1205954"

Navigation menu