Set up a Gitlab instance

We are going to evaluate Gitlab as a replacement for trac, gitweb.tpo, git-rw.tpo, github.com.

This ticket tracks the progress of the setup of a Gitlab service.

cf https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdminTeamMinutes#gitlabservice

Trac:
Child Ticket(s): #33921 (moved), #32730 (moved), #33922 (moved), #30857 (moved), #29401 (moved), #29402 (moved)

added component::internal services/services admin team owner::tpa priority::medium severity::normal status::assigned tickets-migration type::project labels

I don't know Gitlab but if we switch to a new bug tracker, then please one which has built-in features to deal with security bugs. That's the first thing that comes to my mind here.

Trac:
Cc: N/A to gk

For the trac side, be sure to involve gaba, pili, and isa since they have considered our trac requirements.

Replying to gk:

I don't know Gitlab but if we switch to a new bug tracker, then please one which has built-in features to deal with security bugs. That's the first thing that comes to my mind here.

Gitlab have a concept called "confidential issues". Please see: https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html

Trac:
Summary: Evaluation of Gitlab to Set up a Gitlab instance

Trac:
Cc: gk to gk, intrigeri

i don't know what it's worth, but there's a trac to gitlab migration tool that seems it could be useful for us, if we want to move content between the two tools:

https://github.com/tracboat/tracboat

i, for one, would absolutely love to move our issue tracking (and wiki!) there...

Moving this to the Services Admin Team component where it belongs.

Trac:
Component: Internal Services/Tor Sysadmin Team to Internal Services/Services Admin Team

Reassigning to ahf, which is closer to the truth than keeping 'tpa'. Still not perfect. Should there be an email alias for the gitlab service?

Trac:
Owner: tpa to ahf
Status: new to assigned

Hm, yeah, we probably want an alias for gitlab-admins@ for hiro, dgoulet and me. At some point we also need to get a forward setup for git@dip.torproject.org to forward to some postfix instance on the gitlab machine itself, so we can let people modify tickets via email, but let's wait with that.

Current status is that GL is running on https://dip.torproject.org/ but we need to check that everything works. Next step is the LDAP integration.

i believe LDAP integration is complete now, thanks to hiro. LDAP accounts are automatically created (and removed?) based on LDAP, but not passwords - users use the normal gitlab password resets for that part.

i've created a new subticket for the migration issues (#30857 (moved)).

Not close yet until we decide if migrate or not.

Trac:
Owner: ahf to tpa

Trac:
Keywords: N/A deleted, tickets-migration added

mentioned in issue #30857 (moved)

mentioned in issue #32730 (moved)

mentioned in issue #29402 (moved)

mentioned in issue #29401 (moved)

mentioned in issue #33921 (moved)

mentioned in issue #33922 (moved)