Code Quality job startup speed is too slow
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.
- 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".
maybe there's some caching we can do of the docker image that benefits users or pre-fetching the image when the code quality job is in a pipeline?
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.