99 lines
4.8 KiB
Markdown
99 lines
4.8 KiB
Markdown
---
|
|
stage: Verify
|
|
group: Pipeline Authoring
|
|
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
|
|
type: reference
|
|
---
|
|
|
|
# Pipeline Editor **(FREE)**
|
|
|
|
> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4540) in GitLab 13.8.
|
|
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/270059) in GitLab 13.10.
|
|
|
|
The pipeline editor is the primary place to edit the GitLab CI/CD configuration in
|
|
the `.gitlab-ci.yml` file in the root of your repository. To access the editor, go to **CI/CD > Editor**.
|
|
|
|
From the pipeline editor page you can:
|
|
|
|
- Select the branch to work from. [Introduced in GitLab 13.12](https://gitlab.com/gitlab-org/gitlab/-/issues/326189), disabled by default.
|
|
- [Validate](#validate-ci-configuration) your configuration syntax while editing the file.
|
|
- Do a deeper [lint](#lint-ci-configuration) of your configuration, that verifies it with any configuration
|
|
added with the [`include`](../yaml/README.md#include) keyword.
|
|
- See a [visualization](#visualize-ci-configuration) of the current configuration.
|
|
- View an [expanded](#view-expanded-configuration) version of your configuration.
|
|
- [Commit](#commit-changes-to-ci-configuration) the changes to a specific branch.
|
|
|
|
In GitLab 13.9 and earlier, you must already have [a `.gitlab-ci.yml` file](../quick_start/index.md#create-a-gitlab-ciyml-file)
|
|
on the default branch of your project to use the editor.
|
|
|
|
## Validate CI configuration
|
|
|
|
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:
|
|
|
|
|
|
|
|
## Lint CI configuration
|
|
|
|
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](#validate-ci-configuration) 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](../lint.md).
|
|
|
|
|
|
|
|
## Visualize CI configuration
|
|
|
|
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241722) in GitLab 13.5.
|
|
> - [Moved to **CI/CD > Editor**](https://gitlab.com/gitlab-org/gitlab/-/issues/263141) in GitLab 13.7.
|
|
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/290117) in GitLab 13.12.
|
|
|
|
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 [`needs`](../yaml/README.md#needs)
|
|
relationships are displayed as lines connecting jobs together, showing the
|
|
hierarchy of execution:
|
|
|
|
|
|
|
|
Hover over a job to highlight its `needs` relationships:
|
|
|
|
|
|
|
|
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.
|
|
|
|
## View expanded configuration
|
|
|
|
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/246801) in GitLab 13.9.
|
|
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/301103) in GitLab 13.12.
|
|
|
|
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 [`include`](../yaml/README.md#include) is copied into the view.
|
|
- Jobs that use [`extends`](../yaml/README.md#extends) display with the
|
|
[extended configuration merged into the job](../yaml/README.md#merge-details).
|
|
- YAML anchors are [replaced with the linked configuration](../yaml/README.md#anchors).
|
|
|
|
## Commit changes to CI configuration
|
|
|
|
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.
|
|
|
|
|