ReleaseEngineering/How To/Restart burned jobs

< ReleaseEngineering‎ | How To
Revision as of 16:50, 21 December 2014 by Edmorley (talk | contribs) (Bug 1082602)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Restart Burned CI jobs

After planned, or unplanned, disruptions to the continuous integration infrastructure (build farm), there may be jobs which need to be restarted.

There are two approaches: restart individual jobs or restart builds. Both work - use whichever one is easier. Remember to review all "production" branches (twigs/project branches are handled by developers).

Restarting Jobs

  • look on Treeherder for any red, orange, or purple jobs during the event.
  • click on the job link, which will bring up job details in the lower left corner
  • click on the "+" icon at the end of the job name

Restarting Builds

  • look on Treeherder for any red, orange, or purple jobs during the event.
  • click on the light gray "Self-serve Build API" link on the right side of the build title
  • copy the revision shown there to the "Create new dep build..." form at the bottom
  • submit the rebuild.