Connect - Continuous Delivery Platform

Before you provision anything Jenkins needs SSH keys so that it can checkout code from GitHub. Generate SSH keys in the repository folder using ssh-keygen -t rsa -b 4096 -C "your_email@example.com" -N "" and add them to the GitHub account that you would like Jenkins to use.

For a local setup, just run run-minikube.sh. Here’s what will happen:

In order to get the configuration to the Jenkins node there are some initContainers that are run in the pod before starting the main container.

To join all the results and store them across the containers in the pod, the volume ref-volume is used - you can see that it’s mounted as ${JENKINS_HOME}/ref folder to every init container.

Checkout container sets up SSH keys and checks out the repository from GitHub.

Install plugins container installs plugins listed in the plugins file to the ${JENKINS_HOME}/ref folder for Jenkins to pick them up on startup

Override config container updates the Jenkins host and Kubernetes master host values in the config.xml.override using scripts/hack-jenkins-env.sh. Then it copies the updated config to the ${JENKINS_HOME}/ref folder so it’s picked up by Jenkins when it starts up. It also copies scripts/security.groovy to ${JENKINS_HOME}/ref/init.groovy.d/ and when Jenkins starts up it executes all Groovy scripts from that folder. security.groovy sets up the admin user and initial password and Jenkins API token.

Copy jobs container copies predefined job config.xml to ${JENKINS_HOME}/ref folder.

As the Jenkins container starts it runs scripts and copies plugins as described in Jenkins CI Docker image docs. In our setup we avoid running the Jenkins install wizard by setting the environment variable JAVA_OPTS=-Djenkins.install.runSetupWizard=false.

To demonstrate that the environment is working and creating slaves to execute a job, the main container has a postStart hook that runs scripts/wait-for-jenkins-and-run-job.sh that waits until the Jenkins API is available and then triggers a job test that is restricted to run on a slave node. To authenticate, it uses the admin API token that is generated by the scripts/security.groovy.