Sheriffing/How To/Retrigger Jobs: Difference between revisions
(Remove the buildbot rules for triggering Nightlies) |
(Describe how to schedule PGO builds in the brave new Taskcluster world) |
||
| Line 9: | Line 9: | ||
= Retriggering PGO Builds = | = Retriggering PGO Builds = | ||
With the recent switch to Taskcluster-based builds, every push to inbound/autoland now automatically schedules PGO builds for Linux and Windows, so they can be retriggered manually as needed within Treeherder, just like any other failed job. | |||
Release/ESR52 still need to use self-serve to manually schedule PGO builds. Click the "BuildAPI" link on the desired push in Treeherder, copy the push's revision, paste it into the "Create new PGO builds on <tree>" textbox, and click "Submit" to request them. | |||
= Retriggering Nightly Builds = | = Retriggering Nightly Builds = | ||
| Line 22: | Line 20: | ||
'''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. | '''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. | ||
Release/ESR52 still need to use self-serve to manually schedule Nightly builds. Click the "BuildAPI" link on the desired push in Treeherder, copy the push's revision, paste it into the "Create new nightly builds on <tree>" textbox, and click "Submit" to request them. | |||
Revision as of 19:46, 8 August 2017
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
With the recent switch to Taskcluster-based builds, every push to inbound/autoland now automatically schedules PGO builds for Linux and Windows, so they can be retriggered manually as needed within Treeherder, just like any other failed job.
Release/ESR52 still need to use self-serve to manually schedule PGO builds. Click the "BuildAPI" link on the desired push in Treeherder, copy the push's revision, paste it into the "Create new PGO builds on <tree>" textbox, and click "Submit" to request them.
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.
Release/ESR52 still need to use self-serve to manually schedule Nightly builds. Click the "BuildAPI" link on the desired push in Treeherder, copy the push's revision, paste it into the "Create new nightly builds on <tree>" textbox, and click "Submit" to request them.