Closed Bug 1128039 Opened 6 years ago Closed 5 years ago
Autoland to inbound service for Moz
Bug 1086645 is asking that review requests automatically be closed when changesets are made public upon a push to a repository. This is something that can be easily done by Autoland because the request from MozReview to land on an inbound tree will contain the review id. Autoland currently only supports landing to try. Adding the capability to land to inbound is a first step.
autoland: support transplanting to non-Try destinations (bug 1128039) r?gps At the moment, the Autoland code assumes the destination is Try. This patch makes the 'try syntax' optional and adds support for pushing using a bookmark, as well as removing gecko specific naming conventions.
autoland: support push_bookmark in REST endpoints (bug 1128039) r?mdoglio This adds support to for the push_bookmark field in the autoland json structure.
autoland: handle unrecognized trees in treestatus (bug 1128039) r?mdoglio When we start autolanding to non-gecko trees like version-control-tools we need to deal with tree status that isn't present on treestatus.mozilla.org. For now, we'll assume any unrecognized tree is open.
autoland: support longer tree and destination names (bug 1128039) r?mdoglio Turns out 'version-control-tools' is 21 characters, so we should probably support longer source and destination tree names.
autoland: test non-Try destinations (bug 1128039) r?mdoglio
mozreview: rename autoland try tree in mozreview extension (bug 1183295) r?mdoglio
Component: Autoland → MozReview
Product: Tree Management → Developer Services
Target Milestone: --- → Future
Version: --- → unspecified
I'm going to close this one. We've been autolanding to version-control-tools for roughly a month and we've successfully landed to mozilla-inbound and cedar. Bug 1220214 is a tracker for things that need to be fixed prior to turning this on for a larger audience, it makes more sense to file new bugs as blockers there rather than here.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.