Run codequality without requirement for mounting docker socket
Problem
As a devops engineer in an org with a strict security posture, I want to run GitLab's CodeQuality scan without needing to mount a docker socket, so app dev teams can benefit from the Code Quality features.
- For security reasons, customers on self-hosted instances or on dot com with their own runners may disable the privileged option on their runner
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Priyanka (Platform Engineer)
User experience goal
The default code quality template should be widely usable in more situations than it is now, including where:
- Running a privileged runner is undesirable
- Speed of pipeline is important
- Runners are spun up in Kubernetes
Proposal
The SAST job has previously been through this conversion (#10796 (closed)), we may be able to leverage the work that was done there in order to convert the codequality job. However, we may not be able to, since the code climate scan is distributed as an image as mentioned here.
Documentation
CodeQuality documentation would need to be revised to remove mentions of DinD workflow.
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Original
Problem to solve
For security reason, my company disabled the privileged option (https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnersdocker-section).
Cound you please add a way to run codequality and sast without using docker in docker (and without private runner).
Links / references
DinD requirement for SAST was removed with completion of #10796 (closed)