Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
parent
f12dba53d9
commit
2f369bd958
2 changed files with 15 additions and 6 deletions
|
@ -79,6 +79,7 @@ future GitLab releases.**
|
|||
| `CI_MERGE_REQUEST_TARGET_BRANCH_NAME` | 11.6 | all | The target branch name of the merge request if [the pipelines are for merge requests](../merge_request_pipelines/index.md). Available only if `only: [merge_requests]` is used and the merge request is created. |
|
||||
| `CI_MERGE_REQUEST_TARGET_BRANCH_SHA` | 11.9 | all | The HEAD SHA of the target branch of the merge request if [the pipelines are for merge requests](../merge_request_pipelines/index.md). Available only if `only: [merge_requests]` is used, the merge request is created, and the pipeline is a [merged result pipeline](../merge_request_pipelines/pipelines_for_merged_results/index.md). **(PREMIUM)** |
|
||||
| `CI_MERGE_REQUEST_TITLE` | 11.9 | all | The title of the merge request if [the pipelines are for merge requests](../merge_request_pipelines/index.md). Available only if `only: [merge_requests]` is used and the merge request is created. |
|
||||
| `CI_MERGE_REQUEST_EVENT_TYPE` | 12.3 | all | The event type of the merge request, if [the pipelines are for merge requests](../merge_request_pipelines/index.md). Can be `detached`, `merged_result` or `merge_train`. |
|
||||
| `CI_NODE_INDEX` | 11.5 | all | Index of the job in the job set. If the job is not parallelized, this variable is not set. |
|
||||
| `CI_NODE_TOTAL` | 11.5 | all | Total number of instances of this job running in parallel. If the job is not parallelized, this variable is set to `1`. |
|
||||
| `CI_PAGES_DOMAIN` | 11.8 | all | The configured domain that hosts GitLab Pages. |
|
||||
|
|
|
@ -19,12 +19,20 @@ For an introduction to Auto DevOps, watch [AutoDevOps in GitLab 11.0](https://yo
|
|||
|
||||
## Enabled by default
|
||||
|
||||
Starting with GitLab 11.3, the Auto DevOps pipeline is enabled by default for all
|
||||
projects. If it has not been explicitly enabled for the project, Auto DevOps will be automatically
|
||||
disabled on the first pipeline failure. Your project will continue to use an alternative
|
||||
[CI/CD configuration file](../../ci/yaml/README.md) if one is found. A GitLab
|
||||
administrator can [change this setting](../../user/admin_area/settings/continuous_integration.md#auto-devops-core-only)
|
||||
in the admin area.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/41729) in GitLab 11.3.
|
||||
|
||||
Auto DevOps is enabled by default for all projects and will attempt to run on all pipelines
|
||||
in each project. This default can be enabled or disabled by an instance administrator in the
|
||||
[Auto DevOps settings](../../user/admin_area/settings/continuous_integration.md#auto-devops-core-only).
|
||||
It will be automatically disabled in individual projects on their first pipeline failure,
|
||||
if it has not been explicitly enabled for the project.
|
||||
|
||||
Since [GitLab 12.7](https://gitlab.com/gitlab-org/gitlab/issues/26655), Auto DevOps
|
||||
will run on pipelines automatically only if a [`Dockerfile` or matching buildpack](#auto-build)
|
||||
exists.
|
||||
|
||||
If a [CI/CD configuration file](../../ci/yaml/README.md) is present in the project,
|
||||
it will continue to be used, whether or not Auto DevOps is enabled.
|
||||
|
||||
## Quick start
|
||||
|
||||
|
|
Loading…
Reference in a new issue