diff options
Diffstat (limited to 'doc/ci/pipelines/index.md')
| -rw-r--r-- | doc/ci/pipelines/index.md | 42 |
1 files changed, 20 insertions, 22 deletions
diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md index 27e968c0a40..731cb196eaa 100644 --- a/doc/ci/pipelines/index.md +++ b/doc/ci/pipelines/index.md @@ -74,7 +74,7 @@ You can also configure specific aspects of your pipelines through the GitLab UI. - [Pipeline settings](settings.md) for each project. - [Pipeline schedules](schedules.md). -- [Custom CI/CD variables](../variables/README.md#creating-a-custom-environment-variable). +- [Custom CI/CD variables](../variables/README.md#custom-environment-variables). ### View pipelines @@ -82,7 +82,7 @@ You can find the current and historical pipeline runs under your project's **CI/CD > Pipelines** page. You can also access pipelines for a merge request by navigating to its **Pipelines** tab. - + Clicking a pipeline will bring you to the **Pipeline Details** page and show the jobs that were run for that pipeline. From here you can cancel a running pipeline, @@ -93,6 +93,12 @@ latest pipeline for the last commit of a given branch is available at `/project/ Also, `/project/pipelines/latest` will redirect you to the latest pipeline for the last commit on the project's default branch. +[Starting in GitLab 13.0](https://gitlab.com/gitlab-org/gitlab/-/issues/215367), +you can filter the pipeline list by: + +- Trigger author +- Branch name + ### Run a pipeline manually Pipelines can be manually executed, with predefined or manually-specified [variables](../variables/README.md). @@ -153,7 +159,7 @@ You can do this straight from the pipeline graph. Just click the play button to execute that particular job. For example, your pipeline might start automatically, but it requires manual action to -[deploy to production](../environments.md#configuring-manual-deployments). In the example below, the `production` +[deploy to production](../environments/index.md#configuring-manual-deployments). In the example below, the `production` stage has a job with a manual action.  @@ -216,7 +222,7 @@ In the example: Visually, it can be viewed as: -```text +```plaintext 0 1 2 3 4 5 6 7 AAAAAAA BBBBBBB @@ -225,7 +231,7 @@ Visually, it can be viewed as: The union of A, B, and C is (1, 4) and (6, 7). Therefore, the total running time is: -```text +```plaintext (4 - 1) + (7 - 6) => 4 ``` @@ -343,7 +349,7 @@ build ruby 2/3: stage: build script: - echo "ruby2" - + build ruby 3/3: stage: build script: @@ -367,10 +373,14 @@ evaluates the job names: `\d+[\s:\/\\]+\d+\s*`. When running manual jobs you can supply additional job specific variables. You can do this from the job page of the manual job you want to run with -additional variables. +additional variables. To access this page, click on the **name** of the manual job in +the pipeline view, *not* the play (**{play}**) button. -This is useful when you want to alter the execution of a job by using -environment variables. +This is useful when you want to alter the execution of a job that uses +[custom environment variables](../variables/README.md#custom-environment-variables). +Adding a variable name (key) and value here will override the value defined in +[the UI or `.gitlab-ci.yml`](../variables/README.md#custom-environment-variables), +for a single run of the manual job.  @@ -387,7 +397,7 @@ For example, if you start rolling out new code and: - Users do not experience trouble, GitLab can automatically complete the deployment from 0% to 100%. - Users experience trouble with the new code, you can stop the timed incremental rollout by canceling the pipeline - and [rolling](../environments.md#retrying-and-rolling-back) back to the last stable version. + and [rolling](../environments/index.md#retrying-and-rolling-back) back to the last stable version.  @@ -545,15 +555,3 @@ To illustrate its life cycle: even if the commit history of the `example` branch has been overwritten by force-push. 1. GitLab Runner fetches the persistent pipeline ref and gets source code from the checkout-SHA. 1. When the pipeline finished, its persistent ref is cleaned up in a background process. - -NOTE: **NOTE**: At this moment, this feature is on by default and can be manually disabled -by disabling `depend_on_persistent_pipeline_ref` feature flag. If you're interested in -manually disabling this behavior, please ask the administrator -to execute the following commands in rails console. - -```shell -> sudo gitlab-rails console # Login to Rails console of GitLab instance. -> project = Project.find_by_full_path('namespace/project-name') # Get the project instance. -> Feature.disable(:depend_on_persistent_pipeline_ref, project) # Disable the feature flag for specific project -> Feature.disable(:depend_on_persistent_pipeline_ref) # Disable the feature flag system-wide -``` |