Auto-tools/Projects/Autoland: Difference between revisions

Auto-tools/Projects/Autoland (view source)

Revision as of 18:38, 16 December 2014

1,794 bytes added , 16 December 2014

→‎Milestone 1: Update with work accomplished in 2014Q4

Dminor

Confirmed users

313

edits

@@ Line 24: / Line 24: @@
 target delivery date: 2014Q4
-status: in alpha testing, see https://groups.google.com/forum/#!topic/mozilla.tools/sOtaq0P0XHk
+status: We deployed an initial version of Autoland that is able to listen to try pushes and utilize the RelEng Transplant tool to transplant successful try pushes from Try to a clone of mozilla-central hosted on a staging instance of the Transplant tool. Transplant is still under active development and is not ready to be deployed, which necessitated testing against a staging instance and a lcocal clone of mozilla-central.
+When pushing autoland patches to try it is necessary that the head patch be empty and that the commit message contains the try syntax along with the string '--autoland'.
+An example of a summary for an autoland push is:
+    try: -b do -p all -u all -t none --autoland
+    Bug XXXXXX - Do interesting stuff; r=yyy
+The autoland tool does not mandate a minimal set of tests for a change or check that the patch has been properly reviewed. In order to keep autoland as simple as possible it is assumed that these policies will be enforced elsewhere, for instance, in Mozreview. A check is done to verify that the person who pushed to try is a member of the appropriate LDAP group to land on the destination repository, i.e. scm level 3 in order to land on mozilla-inbound.
+A single failure is allowed for each build and test. In this case, autoland automatically retriggers the job to see if it will succeed on the second attempt. If it succeeds on the second run, it is assumed that the failure was intermittent and that the patch can be landed. If two failures occur for any build or test, the autoland request fails.
+If the autoland request succeeds, the transplant tool is used to land the changes. Whether or not the request succeeds, the bugzilla bug corresponding to the request is updated.
+In the next milestone, the plan is to tackle integration with MozReview and focus on landing patches from MozReview to Try and monitoring and reporting the results.
 <bugzilla>