Update documentation regarding Ci Linter
This commit is contained in:
parent
56c95fb6a1
commit
6767dd92da
2 changed files with 5 additions and 4 deletions
|
@ -104,8 +104,8 @@ Jobs are used to create jobs, which are then picked by
|
|||
|
||||
What is important is that each job is run independently from each other.
|
||||
|
||||
If you want to check whether your `.gitlab-ci.yml` file is valid, there is a
|
||||
Lint tool under the page `/ci/lint` of your GitLab instance. You can also find
|
||||
If you want to check whether the `.gitlab-ci.yml` of your project is valid, there is a
|
||||
Lint tool under the page `/ci/lint` of your project namespace. You can also find
|
||||
a "CI Lint" button to go to this page under **CI/CD ➔ Pipelines** and
|
||||
**Pipelines ➔ Jobs** in your project.
|
||||
|
||||
|
|
|
@ -1526,8 +1526,9 @@ capitalization, the commit will be created but the pipeline will be skipped.
|
|||
|
||||
## Validate the .gitlab-ci.yml
|
||||
|
||||
Each instance of GitLab CI has an embedded debug tool called Lint.
|
||||
You can find the link under `/ci/lint` of your gitlab instance.
|
||||
Each instance of GitLab CI has an embedded debug tool called Lint, which validates the
|
||||
content of your `.gitlab-ci.yml` files. You can find the Lint under the page `ci/lint` of your
|
||||
project namespace (e.g, `http://gitlab-example.com/gitlab-org/project-123/ci/lint`)
|
||||
|
||||
## Using reserved keywords
|
||||
|
||||
|
|
Loading…
Reference in a new issue