Instrument CI_DEPLOY_USER, CI_DEPLOY_PASSWORD usage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Currently, GitLab auto-injects the CI_DEPLOY_USER, CI_DEPLOY_PASSWORD environment variables into jobs is a project or deploy token called gitlab-deploy-token is available.

Based on the documentation, the primary goal for these tokens is to allow pushing containers to the GitLab registry. It can be used to work with the same project depending on the access rights given to the deploy token.

In order to focus our efforts better, we would like to know how often is this functionality used.

Proposal

1. Query the gitlab.com database for projects and groups that have a deploy token named gitlab-deploy-token defined, include:
   • project/group tier
   • container registry enabled / disabled
   • containers pushed / month
   • number of pipelines run / month
2. If the numbers show that 5+% of paying accounts use the functionality, add instrumentation for self-managed
3. If the numbers are below 5% of paying accounts, consider removing it