From 943e9f0eb8ad7e19d42b8d33118d8947b119e8c9 Mon Sep 17 00:00:00 2001 From: Tim Beattie <tbeattie@redhat.com> Date: Sun, 29 Apr 2018 23:08:00 +0200 Subject: [PATCH] change "course" to "enablement" --- exercises/2-attack-of-the-pipelines/README.md | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/exercises/2-attack-of-the-pipelines/README.md b/exercises/2-attack-of-the-pipelines/README.md index 87b36f8..4a5ce91 100644 --- a/exercises/2-attack-of-the-pipelines/README.md +++ b/exercises/2-attack-of-the-pipelines/README.md @@ -683,7 +683,7 @@ > _In this exercise we will link GitLab to Jenkins so that new build jobs are triggered on each push to the `develop` branch._ <p class="tip" > -NOTE - This section is optional! Git webhooks are useful but not needed for course completion. +NOTE - This section is optional! Git webhooks are useful but not needed for Enablement completion. </p> 7. In order to allow GitLab trigger Jenkins (because of the OpenShift Auth Plugin), we need to allow the `Anonymous` user trigger builds. Head to your Jenkins Dashboard and click on `Manage Jenkins` on the left hand side. Then scroll down and click `Configure Global Security`. Alternatively, type in `https://jenkins-<YOUR_NAME>-ci-cd.apps.some.domain.com/configureSecurity/` . You should see a screen like so: -- Gitblit v1.9.3