Like the previous quarter ([[ https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201516Q1 | 201516Q1 ]]), to be linked from our [[ https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201516Q2 | 20516Q2 ]] page.
== From our Q2 goals ==
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201516Q2
* Decommission Gitblit - task T111465
* Integrate Differential with our Continuous Integration infrastructure - task T112133
== From the etherpad ==
**STEP 0**: Finish https://phabricator.wikimedia.org/tag/gitblit-deprecate/
* side project: setup github replication from Phabricator
* side project: 1:1 mapping of repo names (gerrit) to callsigns (phab)
**STEP 1**: Write up an RFC of what the ideal arcanist/differential workflow would be.
* use something from RelEng's world as an example, like CI config and/or scap
** mark gerrit repo as read-only and replicate from Phab
* write up "how to install/work with arc" guide
** addresses: https://phabricator.wikimedia.org/T91422
** (probably some more)
** Arc packaging? https://packages.debian.org/sid/arcanist
** just have people git clone arc/libphutil from our fork alongside Phabricator?
** arc upgrade works: https://phabricator.wikimedia.org/P1976
**STEP 2**: CI CI CI
* Herald + Harbormaster + Jenkins seems easiest
** Harbormaster is the new Zuul
* Rough CI plan (Mukunda to diagram):
** Differential revision is posted
** Herald calls the appropriate build plan in Harbormaster
** Harbormaster calls out to appropriate jenkins endpoint(s)
** Jenkins does $stuff
** Jenkins responds (via Conduit?) to the differential with the build result(s)