2019-05-27 15:53:21 -04:00
---
2020-05-29 14:08:26 -04:00
stage: Verify
2021-05-26 11:10:57 -04:00
group: Pipeline Execution
2020-11-26 01:09:20 -05:00
info: 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
2019-06-07 04:00:41 -04:00
type: howto
2019-05-27 15:53:21 -04:00
---
2021-06-21 20:07:53 -04:00
# How to enable or disable GitLab CI/CD **(FREE)**
2016-01-06 14:05:22 -05:00
2019-06-07 04:00:41 -04:00
To effectively use GitLab CI/CD, you need:
2021-06-28 17:10:13 -04:00
- A valid [`.gitlab-ci.yml` ](yaml/index.md ) file present at the root directory
2019-06-07 04:00:41 -04:00
of your project.
2021-06-28 08:38:12 -04:00
- A [runner ](runners/index.md ) properly set up.
2019-06-07 04:00:41 -04:00
2021-02-08 07:09:20 -05:00
You can read our [quick start guide ](quick_start/index.md ) to get you started.
2016-01-06 14:05:22 -05:00
2021-08-23 14:11:07 -04:00
If you use an external CI/CD server like Jenkins or Drone CI, you should
disable GitLab CI/CD to avoid conflicts with the commits status
2016-01-06 14:05:22 -05:00
API.
2021-07-30 23:09:05 -04:00
GitLab CI/CD is exposed by using the `/pipelines` and `/jobs` pages of a project.
2017-10-03 09:11:49 -04:00
Disabling GitLab CI/CD in a project does not delete any previous jobs.
In fact, the `/pipelines` and `/jobs` pages can still be accessed, although
2017-02-03 13:24:17 -05:00
it's hidden from the left sidebar menu.
2016-01-06 14:05:22 -05:00
2021-08-23 14:11:07 -04:00
GitLab CI/CD is enabled by default on all new projects. You can:
2019-06-07 04:00:41 -04:00
2021-08-23 14:11:07 -04:00
- Disable GitLab CI/CD [under each project's settings ](#enable-cicd-in-a-project ).
- Set GitLab CI/CD to be [disabled in all new projects on an instance ](../administration/cicd.md ).
2016-01-06 14:05:22 -05:00
2020-11-18 13:09:08 -05:00
This only applies to pipelines run as part of GitLab CI/CD. This doesn't enable or disable
2020-03-30 17:08:01 -04:00
pipelines that are run from an [external integration ](../user/project/integrations/overview.md#integrations-listing ).
2019-10-01 20:06:26 -04:00
2021-08-23 14:11:07 -04:00
## Enable CI/CD in a project
2016-01-06 14:05:22 -05:00
2021-07-30 23:09:05 -04:00
To enable or disable GitLab CI/CD pipelines in your project:
2019-10-01 20:06:26 -04:00
2021-07-30 23:09:05 -04:00
1. On the top bar, select **Menu > Projects** and find your project.
1. On the left sidebar, select **Settings > General** .
1. Expand **Visibility, project features, permissions** .
2021-08-18 11:11:07 -04:00
1. In the **Repository** section, turn on or off **CI/CD** as required.
2019-12-08 22:07:57 -05:00
2020-11-18 13:09:08 -05:00
**Project visibility** also affects pipeline visibility. If set to:
2019-12-08 22:07:57 -05:00
- **Private**: Only project members can access pipelines.
- **Internal** or **Public** : Pipelines can be set to either **Only Project Members**
2021-07-30 23:09:05 -04:00
or **Everyone With Access** by using the dropdown box.
2019-10-01 20:06:26 -04:00
Press **Save changes** for the settings to take effect.
2016-01-06 14:05:22 -05:00
2019-06-07 04:00:41 -04:00
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Each scenario can be a third-level heading, e.g. `### Getting error message X` .
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->
