Sheriffing/How:To:Retrigger PGO Builds: Difference between revisions
No edit summary |
|||
| Line 9: | Line 9: | ||
and submit this field and you are done | and submit this field and you are done | ||
As of Jan 17, 2017 Linux and Android nightly builds 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#How_do_I_re-spin_mozilla-central_nightlies.3F | |||
Revision as of 19:44, 20 January 2017
Retrigger PGO/Nightly Builds
(note the how-do below can also be adapted for Nightly Builds, but please talk with a sheriff first before retrigger nightly builds)
It might happens that PGO Builds (PGO stands for profile-guided optimization) get busted. When you fix the bustage (with a backout or the developer fix the problem) you can Trigger PGO Build to verify that the issue is fixed.
To fix this go to tbpl self serve like https://secure.pub.build.mozilla.org/buildapi/self-serve/mozilla-central/rev/{your fixed revision} and enter the revision of the pgo builds you want to trigger into the
Create new PGO builds on mozilla-central revision field
and submit this field and you are done
As of Jan 17, 2017 Linux and Android nightly builds 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#How_do_I_re-spin_mozilla-central_nightlies.3F