Confirmed users
709
edits
Phabricator: Difference between revisions
about splinter
(Created page with "= Phabricator at Mozilla = In May 2017 the Engineering Operations team announced that code-review functionality in BMO and MozReview will be fully replaced by Differential, P...") |
(about splinter) |
||
| (14 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Phabricator at Mozilla = | = Phabricator at Mozilla = | ||
Mozilla runs a Phabricator instance at https://phabricator.services.mozilla.com/, mainly for code review. It is currently the preferred solution for code review. [[EngineeringProductivity/Projects/MozReview|MozReview]] was decommissioned in 2018Q3, and Splinter has been decommissioned in 2019. | |||
= FAQ = | Also see [[Lando]], an automatic code-landing system integrated with Phabricator. | ||
Phabricator and Lando are maintained by the [[Engineering Workflow]] team. | |||
= Documentation = | |||
User documentation for Mozilla's Phabricator instance is available on [https://moz-conduit.readthedocs.io/en/latest/ Read the Docs]. There is also a [[/FAQ|user FAQ]] for Phabricator and Lando. | |||
= Operations and Testing = | |||
* [[Phabricator/UpgradeProcess|Upgrade process]] | |||
* [[Phabricator/TestPlan|Test plan]] | |||
= Background = | |||
== Why the change? == | == Why the change? == | ||
| Line 19: | Line 31: | ||
# Deployment of a central Differential (code review) installation, supported by CloudOps, along with supporting tools like Diffusion (repository browser) and Herald (event-driven notifications). We will continue to use our Bugzilla instance, bugzilla.mozilla.org (aka BMO), for issue tracking for the foreseeable future. | # Deployment of a central Differential (code review) installation, supported by CloudOps, along with supporting tools like Diffusion (repository browser) and Herald (event-driven notifications). We will continue to use our Bugzilla instance, bugzilla.mozilla.org (aka BMO), for issue tracking for the foreseeable future. | ||
# Lightweight integration of Differential with BMO. This will include | # Lightweight integration of Differential with BMO. This will include | ||
#* | #* BMO integration, as discussed above. | ||
#* Integration with the Autoland service, which is currently used for around 50% of commits to mozilla-central and an integral part of the Quantum Stylo project. | |||
#* Integration with | |||
== What will happen to Splinter and MozReview? == | == What will happen to Splinter and MozReview? == | ||
| Line 29: | Line 38: | ||
After a short trial period, MozReview will be shut down, and Splinter will be turned off for the main Firefox products on BMO: Core, Firefox, and Toolkit. Contribution guides and documentation will be updated to refer to Phabricator for code-change submissions. The exact archival procedures are will be figured out soon. | After a short trial period, MozReview will be shut down, and Splinter will be turned off for the main Firefox products on BMO: Core, Firefox, and Toolkit. Contribution guides and documentation will be updated to refer to Phabricator for code-change submissions. The exact archival procedures are will be figured out soon. | ||
== Will I be able to request customizations | == Will I be able to request customizations to Differential? == | ||
We plan to limit customizations, but not to zero. We’re making this change (to using a third-party tool) to reduce the support burden on internal teams. The fewer customizations we make the more that happens. Any customizations will generally use Phabricator’s Conduit API; extensions will be limited to changes that are not possible to | We plan to limit customizations, but not to zero. We’re making this change (to using a third-party tool) to reduce the support burden on internal teams. The fewer customizations we make the more that happens. Any customizations will generally use Phabricator’s Conduit API; extensions will be limited to changes that are not possible to | ||