gitlab-org--gitlab-foss/doc/ci/enable_or_disable_ci.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

How to enable or disable GitLab CI/CD (FREE)

To use GitLab CI/CD, you need:

• A valid .gitlab-ci.yml file present at the root directory of your project.
• A runner ready to run jobs.

You can read our quick start guide to get you started.

If you use an external CI/CD server like Jenkins or Drone CI, you can disable GitLab CI/CD to avoid conflicts with the commits status API.

GitLab CI/CD is enabled by default on all new projects. You can:

• Disable GitLab CI/CD under each project's settings.
• Set GitLab CI/CD to be disabled in all new projects on an instance.

If you disable GitLab CI/CD in a project:

• The CI/CD item in the left sidebar is removed.
• The /pipelines and /jobs pages are no longer available.
• Existing jobs and pipelines are not deleted. Re-enable CI/CD to access them again.

The project or instance settings do not enable or disable pipelines run in an external integration.

Enable CI/CD in a project

To enable or disable GitLab CI/CD pipelines in your project:

1. On the top bar, select Menu > Projects and find your project.
2. On the left sidebar, select Settings > General.
3. Expand Visibility, project features, permissions.
4. In the Repository section, turn on or off CI/CD as required.

Project visibility also affects pipeline visibility. If set to:

• Private: Only project members can access pipelines.
• Internal or Public: Pipelines can be set to either Only Project Members or Everyone With Access by using the dropdown box.

Press Save changes for the settings to take effect.