diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-01 09:09:59 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-01 09:09:59 +0300 |
| commit | a7e81add72ecfbbf888ec4f73debdc2647b059de (patch) | |
| tree | 3139b36451667bdd07181ef35044bd9903424fb1 /doc/ci/migration | |
| parent | 4ed4dc08a806773e5dc326fc0c18bda6f6ea7af7 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/migration')
| -rw-r--r-- | doc/ci/migration/jenkins.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/migration/jenkins.md b/doc/ci/migration/jenkins.md index a7ec085a6b2..1130c11f472 100644 --- a/doc/ci/migration/jenkins.md +++ b/doc/ci/migration/jenkins.md @@ -83,7 +83,7 @@ There are some high level differences between the products worth mentioning: - You can control which jobs run in which cases, depending on how they are triggered, with the [`rules` syntax](../yaml/README.md#rules). -- GitLab [pipeline scheduling concepts](../pipelines/schedules.md) are also different than with Jenkins. +- GitLab [pipeline scheduling concepts](../pipelines/schedules.md) are also different from Jenkins. - You can reuse pipeline configurations using the [`include` keyword](../yaml/README.md#include) and [templates](#templates). Your templates can be kept in a central repository (with different permissions), and then any project can use them. This central project could also |