Arch Forum 2024-12-19¶

Participants: Backend devs, Magnus, Victor and Zak

Agenda¶

GitHub migration Retro

GitHub migration Retro¶

We held a retro of both the migration process itself, but also how everything works currently, what works well and what could be improved. In the end there was a vote and a discussion.

Summary¶

Went well / Works well¶

Pipelines feels faster (both because of pipeline itself being faster, but also because less waiting for agents)
The process to migrate felt well prepared, i.e. the guideline, quick reviews of migration PRs from the backend, great support from platform team etc. (Excluding the few first migrations which was a bit of a mess)
The UI is mostly an improvement when used to it
Nice with the cleanup we've done at the same time (naming, pipeline yaml etc).

What doesn't work well / can be improved¶

(only those with at least 1 vote)
- Overview of pipelines (8 votes): What's missing the most is a overview of CICD pipelines from all (or a filtered subset) of backend repos, showing their latest status. (the overview on a specific repo could be improved as well, but this is less important, it's already decent)
- Merge before pipeline pass (6 votes): Currently its possible to merge a PR as soon as it has been reviewed, regardless of the state of pr pipeline. This is a huge risk!
- Does everything work? (5 votes): We are not confident everything works. We should at minimum make sure to deploy all areas to prod at least once on GitHub. Another issue is that its easy to miss the buildDb config flag, which is difficult to spot.
- Migration leftovers (3 votes): Basically everything backend uses would be nice to have in GH (docs, configuration, temp db access pipeline, nuget feed)
- The slack postings of PRs (3 votes): Its too much stuff. When it posts followups it should only reply to the thread, not also post to channel. Also, it's no need to post the PR full template, the PR title would be enough.
- Rerun just a step in the pipeline (1 vote): Its not easy to rerun just a single step in the pipeline.
- Spammy email notifications (1 vote): They are useless since its too much.

Details¶

Full details here: Reetro.io