- Disable GitLab CI/CD in new projects
- Set the
- Change maximum scheduled pipeline frequency
GitLab administrators can manage the GitLab CI/CD configuration for their instance.
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.ymlfor source installations.
gitlab.rbfor 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:
gitlab.ymlwith your editor and set
## Default project features settings default_projects_features: issues: true merge_requests: true wiki: true snippets: false builds: false
sudo service gitlab restart
For Omnibus GitLab installations:
/etc/gitlab/gitlab.rband add this line:
gitlab_rails['gitlab_default_projects_features_builds'] = false
sudo gitlab-ctl reconfigure
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
To disable directed acyclic graphs (DAG), set the limit to
Scheduled pipelines can be configured with any cron value, but they do not always run exactly when scheduled. An internal process, called the pipeline schedule worker, queues all the scheduled pipelines, but does not run continuously. The worker runs on its own schedule, and scheduled pipelines that are ready to start are only queued the next time the worker runs. Scheduled pipelines can’t run more frequently than the worker.
The default frequency of the pipeline schedule worker is
3-59/10 * * * * (every ten minutes,
0:23, and so on). The default frequency for GitLab.com
is listed in the GitLab.com settings.
To change the frequency of the pipeline schedule worker:
- Edit the
gitlab_rails['pipeline_schedule_worker_cron']value in your instance’s
- Reconfigure GitLab for the changes to take effect.
For example, to set the maximum frequency of pipelines to twice a day, set
to a cron value of
0 */12 * * * (
12:00 every day).