Page MenuHomePhabricator

Basic evaluation of gitea as a repo setup
Closed, DeclinedPublic


Having tried and largely rejected gitlab due to enterprise-edition restrictions around desired features, one of the possible solutions for flexible, cloud-user-event-spawnable repo design is gitea, since it is not locking any features behind paywalls or proprietary licenses. It appears lightweight and simple enough for us to manage and to be able to be instrumented/orchestrated in ways we need.

General checks (if blocked, stop)

  • Do a basic install in toolsbeta and see how it handles things like LDAP (obviously avoiding full LDAP auth inside WMCS userspace). It can do pam auth, which might work.
  • If there's nothing blocking after that step, try adding some additional instrumentation such as a general pipeline to the k8s cluster there.
  • (optional at this stage) Examine OIDC options for individual connection to other services like argo or even a limited k8s view of one's tools.
  • (stretch goal) See if the git mirroring feature would work with gerrit.
  • If you got to this step, good for you. Make a new task to perhaps design a real deploy.

Event Timeline

Bstorm created this task.

Mentioned in SAL (#wikimedia-cloud) [2020-04-10T18:59:08Z] <bstorm_> delete toolsbeta-gitlab-01 and build toolsbeta-workflow-test T249946

Naturally, I'm just banging on this on a vm for now, but will want to move to something like this in a real deploy:

Bstorm added a subscriber: Phamhi.

Not working on this now. @Phamhi feel free to re-open if this becomes useful for push to deploy.