Code Quality job startup speed is too slow on gitlab.com
Problem to solve
As a developer using gitlab.com with the CodeQuality template in my gitlab-ci.yml, I want the code quality to job to startup / start running in about a minute so I can get feedback quickly on my code changes.
Customers have noted that the Code Quality scans that take 1 minute locally are taking 4 or 5 minutes on gitlab.com or even self hosted instances. This seems to be a combination of getting the docker image and starting up the runner.
We know scanning large repositories can just take a long time and are investigating that in another issue.
Intended users
- Sasha (Software Developer) - who is waiting for the pipeline to run.
User experience goal
The user should be able to run a pipeline containing CodeQuality on gitlab.com "quickly".
Proposal
Through the following technical investigation issues we will determine a proposal to resolve this:
- Run CQ without DinD requirement - This resulted in a docs update detailing how to run the CQ job on a private runner without the DinD requirement.
- Technical Investigation: Codequality template job on gitlab.com shared runners is slow - The full comment is here the take away is that it's not feasible to try to do this with the codeclimate engine. The next step is to explore other scanners that can be ran without the DinD requirement in addition to using the GitLab container registry and dependency proxy for faster pull times.
Further details
There has been at least one report of this from a user specific to k8s runners but it's happened with non k8s runners as well.