Tag all CI jobs requiring docker-in-docker
What does this MR do?
Fix job tagging for our CI jobs requiring docker-in-docker.
Since these jobs require privileged runners, we must tag them appropriately. We must also use docker tag exclusively as gitlab-org tag will prevent these jobs from executing on community forks.
Relates to #212193 (closed)
This MR also pins the service to a fixed dind version due to previous issues with instability, see https://about.gitlab.com/releases/2019/07/31/docker-in-docker-with-docker-19-dot-03/ for more details.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team