The DevOps 2.4 Toolkit by Viktor Farcic

Author:Viktor Farcic [Viktor Farcic]
Language: eng
Format: epub
Tags: COM051440 - COMPUTERS / Software Development and Engineering / Tools, COM088000 - COMPUTERS / System Administration / General, COM051230 - COMPUTERS / Software Development and Engineering / General
Publisher: Packt
Published: 2019-11-28T05:32:38+00:00

Figure 6-1: Jenkins setup operating in a single Namespace

Now that Jenkins is up-and-running, we can open it in your favorite browser.

1 open "http://$JENKINS_ADDR"

A note to Windows users

Git Bash might not be able to use the open command. If that's the case, please replace the open command with echo. As a result, you'll get the full address that should be opened directly in your browser of choice.

Since this is the first time we're accessing this Jenkins instance, we'll need to login first. Just as before, the password is stored in the Secret jenkins, under jenkins-admin-password. So, we'll query the secret to find out the password.

1 JENKINS_PASS=$(kubectl -n jenkins \ 2 get secret jenkins \ 3 -o jsonpath="{.data.jenkins-admin-password}" \ 4 | base64 --decode; echo)

5 6 echo $JENKINS_PASS

The output of the latter command should be a random string. As an example, I got Ucg2tab4FK. Please copy it, return to the Jenkins login screen opened in your browser, and use it to authenticate. We did not retrieve the username since it is hard-coded to admin.

We'll leave this admin user as-is since we won't explore authentication methods. When running Jenkins "for real", you should install a plugin that provides the desired authentication mechanism and configure Jenkins to use it instead. That could be LDAP, Google or GitHub authentication, and many other providers. For now, we'll continue using admin as the only god-like user.

Now that we got Jenkins up-and-running, we'll create a pipeline which can be used to test our setup.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.