2.7 KiB
| 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 effectively use GitLab CI/CD, you need:
- A valid
.gitlab-ci.ymlfile present at the root directory of your project. - A runner properly set up.
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 should disable GitLab CI/CD to avoid conflicts with the commits status API.
GitLab CI/CD is exposed by using the /pipelines and /jobs pages of a project.
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
it's hidden from the left sidebar menu.
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.
This only applies to pipelines run as part of GitLab CI/CD. This doesn't enable or disable pipelines that are run from an external integration.
Enable CI/CD in a project
To enable or disable GitLab CI/CD pipelines in your project:
- On the top bar, select Menu > Projects and find your project.
- On the left sidebar, select Settings > General.
- Expand Visibility, project features, permissions.
- 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.