Confirmed users
1,927
edits
Engineering Workflow/Road Map: Difference between revisions
Jump to navigation
Jump to search
Commit series work
(move a couple items to Done) |
(Commit series work) |
||
| Line 5: | Line 5: | ||
== Current == | == Current == | ||
=== | === Better support for commit series in Phabricator and Lando === | ||
The official command-line interface for Phabricator, Arcanist, does not meet the needs of engineering when it comes to first-class support for submitting, updating, and pulling down series of commits. Lando also does not currently support the atomic landing of an entire series of commits. We will build a new command-line interface to Phabricator and extend Lando to better support standard Firefox engineering practices. | |||
Impact: | |||
* Efficiently submit and update commit series, encouraging smaller commits. | |||
* Smoothly land commit series, avoiding repetitive clicking and the possibility of merge conflicts. | |||
* Eventually, ease the contribution pipeline by not requiring the installation of Arcanist, which can be annoying on some platforms (primarily Windows). | |||
=== BMO Auth0 Integration === | |||
Our Bugzilla instance will be tied into Mozilla's Auth0 IAM system, which will allow the linking of BMO accounts to LDAP, Mozillians, etc. | |||
Impact: | Impact: | ||
* | * Easily identify employees, NDAed volunteers, and other contributor groups. | ||
* | * Applications integrated with BMO, e.g. Phabricator, can access users' LDAP accounts and other Mozillian data. | ||
* | * Applications already integrated into Mozilla's IAM system can access Bugzilla user data. | ||
=== Vendor manifests === | === Vendor manifests === | ||
| Line 51: | Line 60: | ||
== Next == | == Next == | ||
=== | === Transplant internal improvements === | ||
The Transplant service is the engine that takes diffs from Phabricator (via Lando) and, until its retirement, MozReview and lands them in the destination repository on behalf of a user. There is some design debt in its architecture and deployability that will benefit future work on related services (particularly Lando). | |||
Impact: | Impact: | ||
* | * Lower maintenance costs. | ||
* | * Easier to develop locally. | ||
* | * Better support from operations. | ||
=== Lando for All === | === Lando for All === | ||