You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contributions are welcome via GitHub pull requests. This document outlines the process to help get your contribution accepted.
4
+
5
+
## Sign off Your Work
6
+
7
+
The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the [DCO](http://developercertificate.org/). Contributors must sign-off that they adhere to these requirements by adding a `Signed-off-by` line to commit messages.
Add Signed-off-by line by the committer at the end of the commit log
20
+
message. The meaning of a signoff depends on the project, but it typically
21
+
certifies that committer has the rights to submit this work under the same
22
+
license and agrees to a Developer Certificate of Origin (see
23
+
http://developercertificate.org/ for more information).
24
+
```
25
+
26
+
## How to Contribute
27
+
28
+
1. Fork this repository, develop, and test your changes
29
+
1. Remember to sign off your commits as described above
30
+
1. Submit a pull request
31
+
32
+
***NOTE***: In order to make testing and merging of PRs easier, please submit changes to multiple charts in separate PRs.
33
+
34
+
### Technical Requirements
35
+
36
+
* Must pass [DCO check](#sign-off-your-work)
37
+
* Must follow [Charts best practices](https://helm.sh/docs/topics/chart_best_practices/)
38
+
* Must pass CI jobs for linting and installing changed charts with the [chart-testing](https://github.com/helm/chart-testing) tool
39
+
* Any change to a chart requires a version bump following [semver](https://semver.org/) principles. See [Immutability](#immutability) and [Versioning](#versioning) below
40
+
41
+
Once changes have been merged, the release job will automatically run to package and release changed charts.
42
+
43
+
### Immutability
44
+
45
+
Chart releases must be immutable. Any change to a chart warrants a chart version bump even if it is only a change to the documentation.
46
+
47
+
### Versioning
48
+
49
+
The chart `version` should follow [semver](https://semver.org/).
50
+
51
+
Charts should start at `1.0.0`. Any breaking (backwards incompatible) changes to a chart should:
52
+
53
+
1. Bump the MAJOR version
54
+
2. In the README, under a section called "Upgrading", describe the manual steps necessary to upgrade to the new (specified) MAJOR version
55
+
56
+
### Community Requirements
57
+
58
+
This project is released with a [Contributor Covenant](https://www.contributor-covenant.org).
59
+
By participating in this project you agree to abide by its terms.
This file documents all notable changes to the Jenkins Helm Chart.
4
+
The release numbering uses [semantic versioning](http://semver.org).
5
5
6
-
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.
6
+
Use the following links to reference issues, PRs, and commits prior to v2.6.0.
The change log until v1.5.7 was auto-generated based on git commits. Those entries include a reference to the git commit to be able to get more details.
12
+
13
+
## 2.6.0 First release in jenkinsci GitHub org
14
+
15
+
Updated README for new location
7
16
8
17
## 2.5.2
9
18
@@ -49,7 +58,7 @@ Add an option to specify pod based on labels that can connect to master if Netwo
49
58
## 2.2.0 increase retry for config auto reload
50
59
51
60
Configure `REQ_RETRY_CONNECT` to `10` to give Jenkins more time to start up.
52
-
https://github.com/kiwigrid/k8s-sidecar
61
+
<https://github.com/kiwigrid/k8s-sidecar>
53
62
54
63
Value can be configured via `master.sidecars.configAutoReload.reqRetryConnect`
55
64
@@ -127,13 +136,13 @@ Add support for overriding Ingress paths via `master.ingress.paths`
127
136
128
137
## 1.20.0
129
138
130
-
Add the following options for configuring the Kubernetes plugin.
139
+
Add the following options for configuring the Kubernetes plugin.
131
140
132
-
- master.slaveDefaultsProviderTemplate
133
-
- master.slaveJenkinsUrl
134
-
- master.slaveJenkinsTunnel
135
-
- master.slaveConnectTimeout
136
-
- master.slaveReadTimeout
141
+
- master.slaveDefaultsProviderTemplate
142
+
- master.slaveJenkinsUrl
143
+
- master.slaveJenkinsTunnel
144
+
- master.slaveConnectTimeout
145
+
- master.slaveReadTimeout
137
146
138
147
## 1.19.0
139
148
@@ -265,7 +274,7 @@ Update docs for Helm 3
265
274
266
275
Make `jenkins-home` attachable to Azure Disks without pvc
As a result of the label changes also the selectors of the deployment have been updated.
754
763
Those are immutable so trying an updated will cause an error like:
755
764
756
-
```
765
+
```text
757
766
Error: Deployment.apps "jenkins" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/component":"jenkins-master", "app.kubernetes.io/instance":"jenkins"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
758
767
```
759
768
760
769
In order to upgrade, delete the Jenkins Deployment before upgrading:
0 commit comments