Tree Rules/Integration: Difference between revisions

Tree Rules/Integration (view source)

30 bytes removed , 14 December 2011

m

add link to qbackout extension

Confirmed users

595

edits

@@ Line 38: / Line 38: @@
 ** Bustage is backed out right away. There's no "we'll let you fix this tree while everybody stands by".
 ** If it's not possible to identify the guilty changeset, the sheriffs may backout more changesets to minimize the overhead/time to fix the tree. The innocent ones will be relanded by the sheriff once the bustage is cleared or, in case of doubts, a Try server run will be requested in the bug, before the next landing.
-** See ehsan's blogpost on how to [http://ehsanakhgari.org/blog/2010-09-09/backing-out-multiple-consecutive-changesets-mercurial back out multiple consecutive changesets], or mak's [https://wiki.mozilla.org/User:Mak77 backout shell script] (it will bail out on complicate backouts involving conflicts, those few ones should be done manually).
+** See ehsan's blogpost on how to [http://ehsanakhgari.org/blog/2010-09-09/backing-out-multiple-consecutive-changesets-mercurial back out multiple consecutive changesets], or mak's [https://wiki.mozilla.org/User:Mak77 backout shell script] or Sfink's [https://bitbucket.org/sfink/qbackout qbackout Hg extension].
 * About once a day or more, merge a green mozilla-inbound push with valid PGO results to mozilla-central.
 ** If the push includes compiled files or changes to configure/Makefiles it must have green PGO builds. Otherwise, the first push before it including such changes must have them.