gitlab-org--gitlab-foss/doc/administration/cicd.md

stage	group	info	type
Verify	Pipeline Execution	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments	howto

GitLab CI/CD instance configuration (FREE SELF)

GitLab administrators can manage the GitLab CI/CD configuration for their instance.

Disable GitLab CI/CD in new projects

GitLab CI/CD is enabled by default in all new projects on an instance. You can set CI/CD to be disabled by default in new projects by modifying the settings in:

• gitlab.yml for source installations.
• gitlab.rb for Omnibus GitLab installations.

Existing projects that already had CI/CD enabled are unchanged. Also, this setting only changes the project default, so project owners can still enable CI/CD in the project settings.

For installations from source:

1. Open gitlab.yml with your editor and set builds to false:

   ## Default project features settings
   default_projects_features:
     issues: true
     merge_requests: true
     wiki: true
     snippets: false
     builds: false
   

2. Save the gitlab.yml file.

3. Restart GitLab:

   sudo service gitlab restart
   

For Omnibus GitLab installations:

1. Edit /etc/gitlab/gitlab.rb and add this line:

   gitlab_rails['gitlab_default_projects_features_builds'] = false
   

2. Save the /etc/gitlab/gitlab.rb file.

3. Reconfigure GitLab:

   sudo gitlab-ctl reconfigure
   

Set the needs: job limit (FREE SELF)

The maximum number of jobs that can be defined in needs: defaults to 50.

A GitLab administrator with access to the GitLab Rails console can choose a custom limit. For example, to set the limit to 100:

Plan.default.actual_limits.update!(ci_needs_size_limit: 100)

To disable directed acyclic graphs (DAG), set the limit to 0.