Sheriffing/How To/Retrigger Jobs

Sometimes builds and tests need to be retriggered. For some classes of automation/infrastructure failures, this happens automatically and the job is marked in the Treeherder UI as dark blue. For other cases, or if you're doing investigative work e.g. testing for an intermittent failure, you'll need to retrigger the job manually.

Manual retriggers

• Select a job result in Treeherder and click on it.
• This will display a results pane in the left bottom corner with information like Job, Machine, Task, etc.
• To retrigger this job/test, click on the circular arrow with the mouseover text of "Repeat the selected job" at the top of the results pane and the job will be retriggered. You can accomplish the same thing by simply pressing "r" in the results pane when you are logged in to Treeherder.

Retriggering PGO Builds

PGO (Profile-Guided O'ptimization) builds can break, just like anything else. When you fix the bustage with a backout or with help from a developer, you can trigger PGO builds to verify that the issue is fixed.

To retrigger PGO builds on your changeset:

• Go the buildapi self-serve page for mozilla-central: https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-central
• Input your changeset into the box labelled "Create new PGO builds on mozilla-central revision" at the bottom of the page.
• Click Submit

Retriggering Nightly Builds

As of Jul 26, 2017 nightly builds for all platforms on m-c are now running in taskcluster so the instructions on how to respin them have been updated for these platforms See https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Other_Duties#Nightlies

CAVEAT: there are implications to triggering too many Nightly builds in a single day or in quick succession. Please talk with a sheriff first before retriggering Nightly builds.