diff options
Diffstat (limited to 'doc/ci/pipelines/index.md')
| -rw-r--r-- | doc/ci/pipelines/index.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md index ed0583e0872..f1ca8afa62c 100644 --- a/doc/ci/pipelines/index.md +++ b/doc/ci/pipelines/index.md @@ -80,7 +80,7 @@ You can also configure specific aspects of your pipelines through the GitLab UI. ### Ref specs for runners When a runner picks a pipeline job, GitLab provides that job's metadata. This includes the [Git refspecs](https://git-scm.com/book/en/v2/Git-Internals-The-Refspec), -which indicate which ref (branch, tag, and so on) and commit (SHA1) are checked out from your +which indicate which ref (such as branch or tag) and commit (SHA1) are checked out from your project repository. This table lists the refspecs injected for each pipeline type: @@ -158,7 +158,7 @@ The pipeline now executes the jobs as configured. You can use the [`description` and `value`](../yaml/index.md#variablesdescription) keywords to define [pipeline-level (global) variables](../variables/index.md#create-a-custom-cicd-variable-in-the-gitlab-ciyml-file) that are prefilled when running a pipeline manually. Use the description to explain -what the variable is used for, what the acceptable values are, and so on. +information such as what the variable is used for, and what the acceptable values are. Job-level variables cannot be pre-filled. @@ -260,7 +260,7 @@ pipelines. > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/24851) in GitLab 12.7. Users with the Owner role for a project can delete a pipeline -by clicking on the pipeline in the **CI/CD > Pipelines** to get to the **Pipeline Details** +by selecting the pipeline in the **CI/CD > Pipelines** to get to the **Pipeline Details** page, then selecting **Delete**.  @@ -301,6 +301,9 @@ preserving deployment keys and other credentials from being unintentionally accessed. To ensure that jobs intended to be executed on protected runners do not use regular runners, they must be tagged accordingly. +Review the [deployment safety](../environments/deployment_safety.md) +page for additional security recommendations for securing your pipelines. + ## Trigger a pipeline when an upstream project is rebuilt **(PREMIUM)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9045) in GitLab 12.8. |