Extend GitLab imports to migrate project CI/CD settings

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

• Close this issue

Overview

Currently, only the following project CICD settings are migrated as part of GitLab imports (file-based and direct-transfer):

  ci_cd_settings:
    - :group_runners_enabled
    - :runner_token_expiration_interval
    - :default_git_depth

As GitLab features are expanded, so do the project CICD settings that should be part of the imports.

Aligning project level settings requires substantial effort, especially if there are thousands of them.

Some, more prominent ones, to highlight, are

General pipelines

Job token permissions

NOTE: Job token permissions should not include the (deprecated) https://docs.gitlab.com/ci/jobs/ci_job_token/#limit-your-projects-job-token-access-deprecated

Other CICD settings

Add all the CI/CD settings features during import, listing out the important ones below

• Auto DevOps
• Protected environments
• Artifacts
• Automatic deployment rollbacks
• Deploy freezes
• Pipeline subscriptions

Acceptance Criteria

Successful migration of features:

• General pipelines
• Auto DevOps
• Protected environments
• Artifacts
• Automatic deployment rollbacks
• Deploy freezes
• Job token permissions
• Pipeline subscriptions