ReleaseEngineering/DisposableProjectRepositories: Difference between revisions

ReleaseEngineering/DisposableProjectRepositories (view source)

Revision as of 13:53, 9 February 2021

25 bytes removed , 9 February 2021

no edit summary

Bhearsum

canmove, Confirmed users

6,439

edits

@@ Line 17: / Line 17: @@
 * 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|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'''.
+* 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} 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'''.
 * '''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. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.