GitLab-a-thon was a RelEng & ServiceOps sprint[0]. This email is an update
on what happened during the sprint and what comes next.
Read more on our blog: <
https://phabricator.wikimedia.org/phame/post/view/288/gitlab-a-thon/
____
*Goals*
Our shared goal was deploying a Wikimedia production
service—Blubberoid—from GitLab.
We created the project[1], got our tests working[2], and (eventually) built
an image using BuildKit[3]. And we now have a plan[4] for pushing images to
our production.
- 🟢 Project exists on GitLab
- 🟢 CI Runs on Commits and Merge Requests
- 🟡 We can build an image using GitLab CI
- 🟡 We can deploy a service from GitLab
____
*Next*
- 🟢 Migrate GitLab to beefier hardware[5] (done today by Jelto and
Daniel!)
- 🚧 Enable image pushing from GitLab[6]
- 🚧 GitLab runners for all[7]
- GitLab integrations with IRC/Phab/Slack[8]
As always, happy to chat on libera.chat #wikimedia-gitlab or via email.
Thanks!
– GitLab-a-thon-ers
[0]: <
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/GitLab-a-…
[1]:
<https://gitlab.wikimedia.org/repos/releng/blubber
[2]: <https://gitlab.wikimedia.org/repos/releng/blubber/-/jobs/19021
[3]:
<https://phabricator.wikimedia.org/T307599
[4]: <https://phabricator.wikimedia.org/T308501
____
[5]: <https://phabricator.wikimedia.org/T307142
[6]: <https://phabricator.wikimedia.org/T308271
[7]: <https://phabricator.wikimedia.org/T297426
[8]: <
https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-iz74xowiwuwu…