diff options
Diffstat (limited to 'doc/ci/merge_request_pipelines/index.md')
| -rw-r--r-- | doc/ci/merge_request_pipelines/index.md | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/ci/merge_request_pipelines/index.md b/doc/ci/merge_request_pipelines/index.md index edb5f8c9ff8..e8953d235a7 100644 --- a/doc/ci/merge_request_pipelines/index.md +++ b/doc/ci/merge_request_pipelines/index.md @@ -13,11 +13,11 @@ for merge requests. ## Configuring pipelines for merge requests -To configure pipelines for merge request, add the `only: merge_requests` parameter to -the jobs that you want it to run only for merge requests. +To configure pipelines for merge requests, add the `only: merge_requests` parameter to +the jobs that you want to run only for merge requests. -Then, when developers create or update merge requests, a pipeline runs on -their new commits at every push to GitLab. +Then, when developers create or update merge requests, a pipeline runs +every time a commit is pushed to GitLab. NOTE: **Note**: If you use this feature with [merge when pipeline succeeds](../../user/project/merge_requests/merge_when_pipeline_succeeds.md), @@ -51,10 +51,10 @@ After the merge request is updated with new commits: - The pipeline fetches the latest code from the source branch and run tests against it. In the above example, the pipeline contains only `build` and `test` jobs. -Since the `deploy` job doesn't have the `only: merge_requests` rule, +Since the `deploy` job doesn't have the `only: merge_requests` parameter, deployment jobs will not happen in the merge request. -Pipelines tagged with **merge request** badge indicate that they were triggered +Pipelines tagged with the **merge request** badge indicate that they were triggered when a merge request was created or updated. For example:  @@ -65,16 +65,16 @@ The same tag is shown on the pipeline's details: ## Excluding certain jobs -The behavior of the `only: merge_requests` rule is such that _only_ jobs with -that rule are run in the context of a merge request; no other jobs will be run. +The behavior of the `only: merge_requests` parameter is such that _only_ jobs with +that parameter are run in the context of a merge request; no other jobs will be run. -However, you may want to reverse this behaviour, having all of your jobs to run _except_ +However, you may want to reverse this behavior, having all of your jobs to run _except_ for one or two. Consider the following pipeline, with jobs `A`, `B`, and `C`. Imagine you want: -- All pipelines to always run `A` and `B` -- Only want `C` to run for a merge request, +- All pipelines to always run `A` and `B`. +- `C` to run only for merge requests. To achieve this, you can configure your `.gitlab-ci.yml` file as follows: @@ -102,10 +102,10 @@ C: - merge_requests ``` -Because: +Therefore: -- `A` and `B` are getting the `only:` rule to execute in all cases, they will always run. -- `C` specifies that it should only run for merge requests, it will not run for any pipeline +- Since `A` and `B` are getting the `only:` rule to execute in all cases, they will always run. +- Since `C` specifies that it should only run for merge requests, it will not run for any pipeline except a merge request pipeline. As you can see, this will help you avoid a lot of boilerplate where you'd need |