summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve Azzopardi <sazzopardi@gitlab.com>2019-07-12 13:52:02 +0200
committerSteve Azzopardi <sazzopardi@gitlab.com>2019-07-15 08:52:10 +0200
commit35ec3e5797bfcecfdb47147c9e03dae3181e2ee1 (patch)
treeefab6c1963d5d8913f5def58efd732de78f65048
parent907154957ef89c1f0df1de3c665418146cc93f98 (diff)
downloadgitlab-ce-docs/12733-docs-using-multiple-extends-in-gitlab-ci-yml-introduced-in-gitlab-12.tar.gz
The first MVC of `extends` did not support a job having multiple extends, this was added in GitLab 12.0. closes https://gitlab.com/gitlab-org/gitlab-ee/issues/12733
-rw-r--r--doc/ci/yaml/README.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index c2ef58acf15..851fbe23c3c 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -974,7 +974,7 @@ review_app:
stop_review_app:
stage: deploy
variables:
- GIT_STRATEGY: none
+ GIT_STRATEGY: none
script: make delete-app
when: manual
environment:
@@ -2221,10 +2221,10 @@ spinach:
script: rake spinach
```
-It's also possible to use multiple parents for `extends`.
-The algorithm used for merge is "closest scope wins", so keys
-from the last member will always shadow anything defined on other levels.
-For example:
+In GitLab 12.0 and later, it's also possible to use multiple parents for
+`extends`. The algorithm used for merge is "closest scope wins", so
+keys from the last member will always shadow anything defined on other
+levels. For example:
```yaml
.only-important:
@@ -2644,7 +2644,7 @@ variables:
The value of `GIT_CLONE_PATH` is expanded once into
`$CI_BUILDS_DIR/go/src/namespace/project`, and results in failure
-because `$CI_BUILDS_DIR` is not expanded.
+because `$CI_BUILDS_DIR` is not expanded.
## Special YAML features