Confirmed users
1,927
edits
EngineeringProductivity/Projects/Conduit/RoadMap: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Projects/Conduit/RoadMap (view source)
Revision as of 17:05, 26 June 2017
, 26 June 2017Patch-based Autoland
(Phabricator) |
(Patch-based Autoland) |
||
| Line 6: | Line 6: | ||
Thus the first milestone of the Conduit project is standing up a Phabricator instance. It will be integrated with BMO, although somewhat differently from MozReview. Most notably, Phabricator will support the reviewing of confidential patches. See more on [https://wiki.mozilla.org/Phabricator#BMO_Integration BMO–Phabricator integration]. This involves both operations, to deploy and configure the instance, and development, to build the integration pieces. | Thus the first milestone of the Conduit project is standing up a Phabricator instance. It will be integrated with BMO, although somewhat differently from MozReview. Most notably, Phabricator will support the reviewing of confidential patches. See more on [https://wiki.mozilla.org/Phabricator#BMO_Integration BMO–Phabricator integration]. This involves both operations, to deploy and configure the instance, and development, to build the integration pieces. | ||
At the completion of this stage, we expect Phabricator to be rolled out to some smaller groups. MozReview will continue to be supported. | |||
= Patch-based Autoland = | |||
Given that Autoland is not just one of the more appreciated aspects of MozReview but also part of a larger process-security road map, our first custom service will be a new Autoland service. Whereas the engine that actually does the committing and pushing to repos (the "transplant service") is already a separate service, the logic and UI for submitting Autoland requests and reporting status was built into MozReview and will need to be rewritten. Rewriting this as its own service allows us more control of the user experience, since we are freed from the constraints of Review Board's environment and extension system. This new service is called "Lando" (and is technically two separate microservices, lando-ui and lando-api). | |||
Since we want to deprecate MozReview as quickly as possible, to avoid having three competing code-review tools, Lando will be patch-based, that is, there will be no staging repo for commit submission. In order to fully support the engineering process, Lando needs to support confidential patches, and developing a commit-based system that can handle private commits is a tricky undertaking—one that we will address, but after we have basic autoland support working for all cases. | |||
When this stage is rolled out, Phabricator and the new autoland services will be available for the use of all engineering. MozReview will be considered deprecated and will be made read-only soon after. | |||