GitLab Architectural Spec Written

[jordanh]

Adding support for GitLab is a commonly requested feature and one we're contractually obligated to deliver. We're currently unsure what it would take to implement it. Let's remove this ambiguity.

N.B: @adaniels-parabol can grant the person who takes this issue access to our Gitlab instance

AC

• Spec written in GitHub with high-level proposal on how implementation proceed, see this as an example
• After spec reviewed by Review & Maintainer, Epic created and Issues created (including design and implementation issues) and added to Epic
• Things to consider:
  • Do we only support the cloud-hosted version of GitLab first or both self-hosted and cloud (see: Design: supporting self-hosted services #5567)?
  • Which authentication modes do we support (Oauth, personal, or project tokens? see: Design: supporting self-hosted services #5567)
  • Which API do we use, REST or GraphQL? If GraphQL, can we nest the schema as we do with GitHub?
  • How might our database and GraphQL schemas need to change?
  • What are the impacts to Sprint Poker, to Task pushing?
    - Close Gitlab Integration #3971 along with this issue

EE

• 21 hours

[jordanh]

It might be a good idea to design and implement #5567 and #5563 before tackling this completely. This will allow us to create use the patterns we invent for Jira Server to add "GitLab SaaS" and "Gitlab Self-hosted" at the same time

[jordanh]

Include in next sprint?: Y
See the discussion in Planning for Sprint #​​96

Powered by Parabol

[nickoferrall]

@jordanh I'd be happy to volunteer for this one

[Dschoordsch]

related: #5968

[mattkrick]

From #5567
There's a good image of how self-hosted should look

We may need an additional dropdown at the bottom for them to select an already-existing self-hosted solution that exists within their org, but aside from that it'd be a good jumping off point

From my 1:1 with Nick, we're gonna punt on the above self-hosted business for now & just get the cloud gitlab working with sprint poker.
Since this AC was written back in October before the big ol gitlab PR was merged we can update the AC to include breaking work into issues.

Proposed updated AC @nickoferrall

• Create all the issues required to support GitLab in sprint poker (see GitHub or Jira issues for inspiration). Put them in the Sprint Poker GitLab Milestone. Shoot for each issue to be 8 hours or less
• Include predecessors at the top of each issue description to show what things depend on other things (e.g. creating new gitlab issues likely has a predecessor of Integration task architecture spec'd #5968)
• Create an overarching issue & put it at the top of the milestone (Georg has a good example, see Jira Server Architectural Spec Written #5563 (comment) for inspiration)
• Have a final issue that is to spec out building GitLab Self-Hosted

[mattkrick]

Closing in favor of #6058