Skip to content

Commit 4144a0f

Browse files
committed
Merge branch 'docs/edit-notes-about-remote-includes' into 'master'
Edit note about remote includes Closes #58836 See merge request gitlab-org/gitlab-ce!25999
2 parents 6461cbd + 26171a9 commit 4144a0f

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

doc/ci/yaml/README.md

+5-8
Original file line numberDiff line numberDiff line change
@@ -1703,6 +1703,11 @@ of using YAML anchors, you can use the [`extends` keyword](#extends).
17031703

17041704
See [usage examples](#include-examples).
17051705

1706+
NOTE: **Note:**
1707+
`.gitlab-ci.yml` configuration included by all methods is evaluated at pipeline creation.
1708+
The configuration is a snapshot in time and persisted in the database. Any changes to
1709+
referenced `.gitlab-ci.yml` configuration will not be reflected in GitLab until the next pipeline is created.
1710+
17061711
#### `include:local`
17071712

17081713
`include:local` includes a file from the same repository as `.gitlab-ci.yml`.
@@ -1793,14 +1798,6 @@ include:
17931798
All nested includes will be executed without context as public user, so only another remote,
17941799
or public project, or template is allowed.
17951800

1796-
NOTE: **Note:**
1797-
Changes to remote includes will not have effect on already created pipelines,
1798-
because the include is being evaluated at the time of pipeline creation.
1799-
This is when full definition of CI yaml is being expanded in order to create
1800-
pipeline with stages with jobs. You always retry job that is already created,
1801-
thus created after pipeline creation. To re-include all (thus re-evaluate the
1802-
configuration), you have to re-create pipeline.
1803-
18041801
#### Nested includes
18051802

18061803
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/56836) in GitLab 11.9.

0 commit comments

Comments
 (0)