- Validate CI configuration
- Lint CI configuration
- Visualize CI configuration
- View expanded configuration
- Commit changes to CI configuration
The pipeline editor is the primary place to edit the GitLab CI/CD configuration in
.gitlab-ci.yml file. To access it, go to CI/CD > Editor.
From the pipeline editor page you can:
- Validate your configuration syntax while editing the file.
- Do a deeper lint of your configuration, that verifies it with any configuration
added with the
- See a visualization of the current configuration.
- View an expanded version of your configuration.
- Commit the changes to a specific branch.
.gitlab-ci.ymlfile on the default branch of your project to use the editor.
As you edit your pipeline configuration, it is continually validated against the GitLab CI/CD pipeline schema. It checks the syntax of your CI YAML configuration, and also runs some basic logical validations.
The result of this validation is shown at the top of the editor page. If your configuration is invalid, a tip is shown to help you fix the problem:
To test the validity of your GitLab CI/CD configuration before committing the changes, you can use the CI lint tool. To access it, go to CI/CD > Editor and select the Lint tab.
This tool checks for syntax and logical errors but goes into more detail than the automatic validation in the editor.
The results are updated in real-time. Any changes you make to the configuration are reflected in the CI lint. It displays the same results as the existing CI Lint tool.
- Introduced in GitLab 13.5.
- Moved to CI/CD > Editor in GitLab 13.7.
- It was deployed behind a feature flag, disabled by default.
- Became enabled by default in GitLab 13.8.
- It’s enabled on GitLab.com.
- It’s recommended for production use.
- To use it in GitLab self-managed instances, ask a GitLab administrator to enable it.
To view a visualization of your
gitlab-ci.yml configuration, in your project,
go to CI/CD > Editor, and then select the Visualize tab. The
visualization shows all stages and jobs. Any
relationships are displayed as lines connecting jobs together, showing the
hierarchy of execution:
Hover over a job to highlight its
If the configuration does not have any
needs relationships, then no lines are drawn because
each job depends only on the previous stage being completed successfully.
CI/CD configuration visualization is under development but ready for production use. It is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it.
To disable it:
To enable it:
To view the fully expanded CI/CD configuration as one combined file, go to the pipeline editor’s View merged YAML tab. This tab displays an expanded configuration where:
- Configuration imported with
includeis copied into the view.
- Jobs that use
extendsdisplay with the extended configuration merged into the job.
- YAML anchors are replaced with the linked configuration.
Expanded CI/CD configuration is under development and not ready for production use. It is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to enable it.
To disable it:
To enable it:
The commit form appears at the bottom of each tab in the editor so you can commit your changes at any time.
When you are satisfied with your changes, add a descriptive commit message and enter a branch. The branch field defaults to your project’s default branch.
If you enter a new branch name, the Start a new merge request with these changes checkbox appears. Select it to start a new merge request after you commit the changes.