Deploying Jenkins
Last updated
Was this helpful?
Last updated
Was this helpful?
On third 2nd step, you can see a shell command to config your cluster on your workspace. You can click to the IBM Cloud Shell button on top right and open a shell workspace connected to your cloud environment.
Then you can copy the config command and paste it to your terminal and press enter.
First, we need to create a namespace for Jenkins pods to deploy.
Then we need to create a values.yaml file for jenkins helm chart to read. This file will customize our Jenkins deployment.
storageClass: this config sets the storage class which kubernetes will use when provisioning a persistent volume.
master.customInitContainers: this config sets a new initContainer that runs before the jenkins master and sets the ownership of the binded volume. Without this manipulation, Jenkins will not be able to write to persistent storage.
Deploy Jenkins with the next command. It will take approximately 5-6 minutes.
IBM Cloud Shell uses helm v2. That is why we are configuring tiller in the above step. if you are using helm v3 in your own workspace,
helm install -f values.yaml stable/jenkins jenkins --namespace jenkins
will be the command.
Get auto-generated Jenkins password. Write this password down to somewhere.
Get Jenkins master pod name
Proxy network to Jenkins pod
Open 8080 port from IBM Cloud Shell
Use admin for username and printed password to login on Jenkins