Pipelines settings
To reach the pipelines settings navigate to your project'sSettings ➔ CI/CD.
The following settings can be configured per project.
Git strategy
With Git strategy, you can choose the default way your repository is fetched from GitLab in a job.
There are two options:
- Using
git clonewhich is slower since it clones the repository from scratch for every job, ensuring that the project workspace is always pristine. - Using
git fetchwhich is faster as it re-uses the project workspace (falling back to clone if it doesn't exist).
The default Git strategy can be overridden by theGIT_STRATEGY variablein.gitlab-ci.yml.
Timeout
Timeout defines the maximum amount of time in minutes that a job is able run. The default value is 60 minutes. Decrease the time limit if you want to impose a hard limit on your jobs' running time or increase it otherwise. In any case, if the job surpasses the threshold, it is marked as failed.
Timeout overriding on Runner level
- Introducedin GitLab 10.7.
Project defined timeout (either specific timeout set by user or the default 60 minutes timeout) may beoverridden on Runner level.
自定义CI配置路径
- Introducedin GitLab 9.4.
By default we look for the.gitlab-ci.ymlfile in the project's root directory. If you require a different locationwithinthe repository, you can set a custom filepath that will be used to lookup the config file, this filepath should berelativeto the root.
Here are some valid examples:
- .gitlab-ci.yml
- .my-custom-file.yml
- 我的/道路/ .gitlab-ci.yml
- my/path/.my-custom-file.yml
Test coverage parsing
If you use test coverage in your code, GitLab can capture its output in the job log using a regular expression. In the pipelines settings, search for the "Test coverage parsing" section.
Leave blank if you want to disable it or enter a ruby regular expression. You can usehttp://rubular.comto test your regex.
If the pipeline succeeds, the coverage is shown in the merge request widget and in the jobs table.
A few examples of known coverage tools for a variety of languages can be found in the pipelines settings page.
Visibility of pipelines
Access to pipelines and job details (including output of logs and artifacts) is checked against your current user access level and thePublic pipelinesproject setting under your project'sSettings > CI/CD > General pipelines settings.
IfPublic pipelinesis enabled (default):
- forpublicprojects, anyone can view the pipelines and access the job details (output logs and artifacts)
- forinternalprojects, any logged in user can view the pipelines and access the job details (output logs and artifacts)
- forprivateprojects, any member (guest or higher) can view the pipelines and access the job details (output logs and artifacts)
IfPublic pipelinesis disabled:
- forpublicprojects, anyone can view the pipelines, but only members (reporter or higher) can access the job details (output logs and artifacts)
- forinternalprojects, any logged in user can view the pipelines, but only members (reporter or higher) can access the job details (output logs and artifacts)
- forprivateprojects, only members (reporter or higher) can view the pipelines and access the job details (output logs and artifacts)
Auto-cancel pending pipelines
Introducedin GitLab 9.1.
If you want to auto-cancel all pending non-HEAD pipelines on branch, when new pipeline will be created (after your git push or manually from UI), checkAuto-cancel pending pipelinescheckbox and save the changes.
Pipeline Badges
In the pipelines settings page you can find pipeline status and test coverage badges for your project. The latest successful pipeline will be used to read the pipeline status and test coverage values.
Visit the pipelines settings page in your project to see the exact link to your badges, as well as ways to embed the badge image in your HTML or Markdown pages.
Pipeline status badge
Depending on the status of your job, a badge can have the following values:
- pending
- running
- passed
- failed
- skipped
- canceled
- unknown
You can access a pipeline status badge image using the following link:
https://example.gitlab.com///badges//build.svg Test coverage report badge
GitLab使成为可能define the regular expression forcoverage report, that each job log will be matched against. This means that each job in the pipeline can have the test coverage percentage value defined.
The test coverage badge can be accessed using following link:
https://example.gitlab.com///badges//coverage.svg If you would like to get the coverage report from a specific job, you can add thejob=coverage_job_nameparameter to the URL. For example, the following Markdown code will embed the test coverage report badge of thecoveragejob into yourREADME.md:
