First steps are to define requirements for CI and come up with a plan.
Setting up Differential is straightforward, you just need a .arcconfig file in the repo. The other important part is CI integration. Please let us (Release-Engineering-Team) know what your needs are so that we can help to set it up in the most ideal way possible.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T141159 [Differential] Remove Gerrit support from repo and jobs | |||
| Declined | None | T134505 [Differential] Update repo configuration to enable Differential |
@mmodell, @thcipriani There doesn't seem to be any resistance on the team to exploring Differential. Is it possible to straddle both Gerrit and Differential to help ease our transition? Also, any documentation you can recommend or a canonical repo to mimic would be super helpful! Thanks! :)
Yes, you can certainly straddle the two, that's what we did for scap at first. Basically you'd start out making new diffs in differential (instead of Gerrit) but when you land, you'd push back to Gerrit--which would then mirror back here. When you've finished doing leftover reviews in Gerrit, we can mark that repo read-only, make the one here canonical, and you start pushing here instead.
As far as canonical repos to mimic: rMSCA :)
After some internal discussion, we're tentatively planning to start this early next quarter to avoid impacting our ambitious Feeds goals.
I'd lean toward deprioritizing this until there's more of a drop-in CI solution ready to go.
@Mholloway: CI in differential is a drop-in solution currently, however, I'm not sure if it currently meets the needs of the android team. At any rate, I would be happy to work with you to make sure it's up to the task.