diff options
Diffstat (limited to 'doc/ci/pipelines')
| -rw-r--r-- | doc/ci/pipelines/merge_request_pipelines.md | 11 | ||||
| -rw-r--r-- | doc/ci/pipelines/multi_project_pipelines.md | 2 | ||||
| -rw-r--r-- | doc/ci/pipelines/settings.md | 11 |
3 files changed, 16 insertions, 8 deletions
diff --git a/doc/ci/pipelines/merge_request_pipelines.md b/doc/ci/pipelines/merge_request_pipelines.md index d80b745e6bc..75408de2721 100644 --- a/doc/ci/pipelines/merge_request_pipelines.md +++ b/doc/ci/pipelines/merge_request_pipelines.md @@ -20,19 +20,20 @@ Branch pipelines: - Run when you push a new commit to a branch. - Are the default type of pipeline. - Have access to [some predefined variables](../variables/predefined_variables.md). -- Have access to [protected variables](../variables/index.md#protect-a-cicd-variable). +- Have access to [protected variables](../variables/index.md#protect-a-cicd-variable) and [protected runners](../runners/configure_runners.md#prevent-runners-from-revealing-sensitive-information). Merge request pipelines: - Run when you: - - Create a new merge request. + - Create a new merge request from a source branch with one or more commits. - Push a new commit to the source branch for a merge request. - Select **Run pipeline** from the **Pipelines** tab in a merge request. This option - is only available when merge request pipelines are configured for the pipeline. + is only available when merge request pipelines are configured for the pipeline + and the source branch has at least one commit. - Do not run by default. The jobs in the CI/CD configuration file [must be configured](#prerequisites) to run in merge request pipelines. - Have access to [more predefined variables](#available-predefined-variables). -- Do not have access to [protected variables](../variables/index.md#protect-a-cicd-variable). +- Do not have access to [protected variables](../variables/index.md#protect-a-cicd-variable) or [protected runners](../runners/configure_runners.md#prevent-runners-from-revealing-sensitive-information). Both of these types of pipelines can appear on the **Pipelines** tab of a merge request. @@ -147,7 +148,7 @@ a warning that you must accept before you can trigger the pipeline. Prerequisites: - You must be a member of the parent project and have at least the [Developer role](../../user/permissions.md). -- The fork project must be [visible](../../public_access/public_access.md) to the +- The fork project must be [visible](../../user/public_access.md) to the user running the pipeline. Otherwise, the **Pipelines** tab does not display in the merge request. diff --git a/doc/ci/pipelines/multi_project_pipelines.md b/doc/ci/pipelines/multi_project_pipelines.md index 2163527e3ca..e6af9292fe1 100644 --- a/doc/ci/pipelines/multi_project_pipelines.md +++ b/doc/ci/pipelines/multi_project_pipelines.md @@ -282,7 +282,7 @@ tag in a different project. Prerequisites: -- The upstream project must be [public](../../public_access/public_access.md). +- The upstream project must be [public](../../user/public_access.md). - The user must have the Developer role in the upstream project. diff --git a/doc/ci/pipelines/settings.md b/doc/ci/pipelines/settings.md index 7960d0afa85..b6ea16ae224 100644 --- a/doc/ci/pipelines/settings.md +++ b/doc/ci/pipelines/settings.md @@ -76,7 +76,14 @@ To avoid this scenario: 1. Select the **Skip outdated deployment jobs** checkbox. 1. Select **Save changes**. -Older deployment jobs are skipped when a new deployment starts. +When a new deployment starts, older deployment jobs are skipped. Skipped jobs are labeled: + +- `forward deployment failure` in the pipeline view. +- `The deployment job is older than the previously succeeded deployment job, and therefore cannot be run` + when viewing the completed job. + +Job age is determined by the job start time, not the commit time, so a newer commit +can be skipped in some circumstances. For more information, see [Deployment safety](../environments/deployment_safety.md). @@ -223,7 +230,7 @@ Setting the regular expression this way takes precedence over project settings. WARNING: This feature is in its end-of-life process. It is [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) -for use in GitLab 14.9, and is planned for [removal](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) in GitLab 15.0. +in GitLab 14.9, and is planned for [removal](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) in GitLab 15.0. You can add test coverage results to merge requests using the Project's CI/CD settings: |