diff options
| author | Jason Lenny <jason@gitlab.com> | 2019-08-08 09:02:01 +0000 |
|---|---|---|
| committer | Jason Lenny <jason@gitlab.com> | 2019-08-08 09:02:01 +0000 |
| commit | cf3fba7dd567c7fe6cd9d5b274525f5b50288b0b (patch) | |
| tree | c1dda6ad785cbc7ed67b6e7ef7ca1885daf72af2 | |
| parent | bfd3e0344a82245e5fdbfaf4d4dc9048720660d4 (diff) | |
| download | gitlab-ce-cf3fba7dd567c7fe6cd9d5b274525f5b50288b0b.tar.gz | |
Fix links
| -rw-r--r-- | doc/ci/jenkins/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/jenkins/index.md b/doc/ci/jenkins/index.md index e3f7513573a..f8a3fab88e3 100644 --- a/doc/ci/jenkins/index.md +++ b/doc/ci/jenkins/index.md @@ -42,7 +42,7 @@ and manage. That said, we do of course still value DRY (don't repeat yourself) principles and want to ensure that behaviors of your jobs can be codified once and applied as needed. You can use the `extends:` syntax to -[templatize your jobs](../yaml/#extends), and `include:` can be used to [bring in entire sets of behaviors](../yaml/#include) +[templatize your jobs](../yaml/README.md#extends), and `include:` can be used to [bring in entire sets of behaviors](../yaml/README.md#include) to pipelines in different projects. ```yaml |