CI/CD runner
Problem
We expect to push changes out faster than 2-3 minutes and developers also expect to see feedback about their latest changes that fast.
When using the default, free, shared GitLab runners, we often have to wait several minutes for them to become available and even after that they run for 6-10 minutes. This sums up to 10-15 minutes reaction / feedback time after every change, which is too disruptive.
Solution
The OAX project should host their own, dedicated gitlab-runner
machine,
which has stable network connectivity, decent CPU performance and enough RAM
to keep the CI job time around 2-3 minutes.
Edited by Tamas Herman