From 60c190ef54a732127c229fd43f4974bcfbb0d193 Mon Sep 17 00:00:00 2001 From: Ryan DeBeasi <rdebeasi@redhat.com> Date: Fri, 10 Aug 2018 19:38:16 +0200 Subject: [PATCH] Restore Jenkins blog link --- 1-the-manual-menace/README.md | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/1-the-manual-menace/README.md b/1-the-manual-menace/README.md index 8ba747e..0162872 100644 --- a/1-the-manual-menace/README.md +++ b/1-the-manual-menace/README.md @@ -416,6 +416,7 @@ greenballs:1.15 ```  +Why does Jenkins use blue to represent success? More can be found [on reddit](https://www.reddit.com/r/programming/comments/4lu6q8/why_does_jenkins_have_blue_balls/) or the [Jenkins blog](https://jenkins.io/blog/2012/03/13/why-does-jenkins-have-blue-balls/). 5. Before building and deploying the Jenkins s2i; add git credentials to it. These will be used by Jenkins to access the Git Repositories where our apps will be stored. We want Jenkins to be able to push tags to it so write access is required. There are a few ways we can do this; either adding them to the `template/jenkins.yml` as environment Variables and then including them in the `params/jenkins` file. We could also create a token in GitLab and use it as the source secret in the Jenkins template. But for simplicity just replace the `<USERNAME>` && `<PASSWORD>` in the `jenkins-s2i/configuration/init.groovy` with your LDAP credentials as seen below. This init file gets run when Jenkins launches and will setup the credentials for use in our Jobs in the next exercises -- Gitblit v1.9.3