charts/incubator/jenkins/README.md

Jenkins

Jenkins is widely recognized as the most feature-rich CI available with easy configuration, continuous delivery and continuous integration support, easily test, build and stage your app, and more. It supports multiple SCM tools including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based projects as well as arbitrary scripts.

TL;DR;

$ helm install jenkins-x.x.x.tgz

Introduction

Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads.

This chart bootstraps a Jenkins deployment on a Kubernetes cluster using the Helm package manager.

Get this chart

Download the latest release of the chart from the releases page.

Alternatively, clone the repo if you wish to use the development snapshot:

$ git clone https://github.com/bitnami/charts.git

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release jenkins-x.x.x.tgz

Replace the x.x.x placeholder with the chart release version.

The command deploys Jenkins on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip

: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the Jenkins chart and their default values.

Parameter	Description	Default
imageTag	bitnami/jenkins image tag	Jenkins image version
imagePullPolicy	Image pull policy	Always if imageTag is latest, else IfNotPresent
jenkinsUser	User of the application	nil
jenkinsPassword	Application password	nil

The above parameters map to the env variables defined in bitnami/jenkins. For more information please refer to the bitnami/jenkins image documentation.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set jenkinsUser=my-user,jenkinsPassword=my-password \
    jenkins-x.x.x.tgz

The above command sets the Jenkins admin username and password to my-user and my-password respectively.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml jenkins-x.x.x.tgz

Tip

: You can use the default values.yaml

Persistence

The Bitnami Jenkins image stores the Jenkins data and configurations at the /bitnami/jenkins path of the container.

As a placeholder, the chart mounts an emptyDir volume at this location.

"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."

For persistence of the data you should replace the emptyDir volume with a persistent storage volume, else the data will be lost if the Pod is shutdown.

Step 1: Create a persistent disk

You first need to create a persistent disk in the cloud platform your cluster is running. For example, on GCE you can use the gcloud tool to create a gcePersistentDisk:

$ gcloud compute disks create --size=500GB --zone=us-central1-a jenkins-data-disk

Step 2: Update templates/deployment.yaml

Replace:

      volumes:
      - name: jenkins-data
        emptyDir: {}

with

      volumes:
      - name: jenkins-data
        gcePersistentDisk:
          pdName: jenkins-data-disk
          fsType: ext4

Install the chart after making these changes.