Page MenuHomePhabricator

Outline work (outcomes and outputs) of RelEng's Q2 Gerrit migration work
Closed, ResolvedPublic


Like the previous quarter (201516Q1), to be linked from our 20516Q2 page.

From our Q2 goals

  • Decommission Gitblit - task T111465
  • Integrate Differential with our Continuous Integration infrastructure - task T112133

From the etherpad

STEP 0: Finish

  • 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.


  • 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)

Event Timeline

greg raised the priority of this task from to Medium.
greg updated the task description. (Show Details)
greg added subscribers: greg, Aklapper, mmodell, demon.

Do you think you will need some help from #Engineering-Community during October-December? Just checking for our own planning.

@Qgil: Maybe? I'd love support, most likely. I don't have a firm idea yet (part of this task's work). It might be worth a quick sync up between you, me, mukunda, chad, and andre? Wish you would have been at the manager's offsite these past two days.... :)

greg set Security to None.

Meeting to discuss what the roadmap looks like between "here" and "code review happens in Phab" is scheduled for Thursday morning Pacific with Chad, Mukunda, and Antoine. Purposefully left out anyone from ECT (and myself). We'll come in later. :)

I'll be next week in San Francisco. If you are there as well ;) then I'll just go hunt you early some morning for a Differential chat.

@mmodell, @demon, @hashar:

See the task description for context/current plan of record.

Should our plan of action actually be:


  • decommission gitblit
  • publish and discuss RFC (context in description)
    • sidenote: Should this be talked about that the Dev Summit?
  • Not a mentioned/explicit quarterly goal, but actually doing: CI integration with Differential)


  • Finish CI integration
  • Assuming positive RFC outcome: flip the switch

sidenote: Should this be talked about that the Dev Summit?

The Summit fits perfectly in your timeline. It would make sense to have a session to gather feedback for the RfC, answer to questions, discuss hard problems... in the context of the RfC and the other ongoing discussions.