[stable/jenkins] Update Readme to work with Helm 3 (#20855)

* Update readme and bump chart version
Signed-off-by: Bharath Baiju <bharathkrishnakb@gmail.com>

Signed-off-by: bharathkkb <bharathkrishnakb@gmail.com>

* Update Changelog
Signed-off-by: Bharath Baiju <bharathkrishnakb@gmail.com>

Signed-off-by: bharathkkb <bharathkrishnakb@gmail.com>
This commit is contained in:
Bharath KKB
2020-02-19 05:02:25 -08:00
committed by GitHub
parent 2435a2a26b
commit 94f3bd4490
3 changed files with 9 additions and 5 deletions
+4
View File
@@ -5,6 +5,10 @@ numbering uses [semantic versioning](http://semver.org).
NOTE: The change log until version 1.5.7 is auto generated based on git commits. Those include a reference to the git commit to be able to get more details.
## 1.9.19
Update docs for Helm 3
## 1.9.18
Make `jenkins-home` attachable to Azure Disks without pvc
+1 -1
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: jenkins
home: https://jenkins.io/
version: 1.9.18
version: 1.9.19
appVersion: lts
description: Open source continuous integration server. It supports multiple SCM tools
including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based
+4 -4
View File
@@ -18,7 +18,7 @@ This chart will do the following:
To install the chart with the release name `my-release`:
```bash
$ helm install --name my-release stable/jenkins
$ helm install my-release stable/jenkins
```
## Upgrading an existing Release to a new major version
@@ -220,7 +220,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
$ helm install --name my-release -f values.yaml stable/jenkins
$ helm install my-release -f values.yaml stable/jenkins
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -320,7 +320,7 @@ It is possible to mount several volumes using `persistence.volumes` and `persist
3. Install the chart
```bash
$ helm install --name my-release --set persistence.existingClaim=PVC_NAME stable/jenkins
$ helm install my-release --set persistence.existingClaim=PVC_NAME stable/jenkins
```
#### Storage Class
@@ -328,7 +328,7 @@ $ helm install --name my-release --set persistence.existingClaim=PVC_NAME stable
It is possible to define which storage class to use:
```bash
$ helm install --name my-release --set persistence.storageClass=customStorageClass stable/jenkins
$ helm install my-release --set persistence.storageClass=customStorageClass stable/jenkins
```
If set to a dash (`-`, as in `persistence.storageClass=-`), the dynamic provision is disabled.