Confirmed users
1,905
edits
Auto-tools/Projects/Autoland: Difference between revisions
no edit summary
No edit summary |
|||
| Line 43: | Line 43: | ||
6a - If ok to land, autoland lands the patch in-tree. We may coalesce pending autoland commits and land them in batches periodically, like once per hour, ala Bumper Bot.<br/> | 6a - If ok to land, autoland lands the patch in-tree. We may coalesce pending autoland commits and land them in batches periodically, like once per hour, ala Bumper Bot.<br/> | ||
6b - If not ok to land, Autoland notifies the developer of the problem via bugzilla. | 6b - If not ok to land, Autoland notifies the developer of the problem via bugzilla. | ||
== Components == | |||
=== Autoland Service === | |||
This is the primary component of Autoland. This service monitors pulse for autoland jobs submitted to try, monitors such try jobs for completion using the buildapi, queries Treeherder for job status, and retriggers failing jobs. It also submits comments to Bugzilla when the Autoland status of a try push changes, and lands patches on inbound trees if all success criteria are met. | |||
=== Treeherder === | |||
Treeherder will be utilized in the following ways: | |||
# The Autoland service will request job status (pass/fail) from Treeherder for Autoland try jobs | |||
# Treeherder will expose a special Autoland view of try jobs which need sheriff attention; this view will include a button (available only to privileged users) that will allow a pending Autoland push to be landed or rejected. | |||
=== Releng Buildapi === | |||
This api (which exists already) will be used to determine when Autoland try jobs are finished, and will be used to retrigger failing jobs. | |||
docs: [[ReleaseEngineering/Applications/BuildAPI]] | |||