First release of helm chart in new location

CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+# Code of Conduct
+
+Jenkins Code of Conduct can be found [here](https://www.jenkins.io/project/conduct/).

CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing Guidelines
+
+Contributions are welcome via GitHub pull requests. This document outlines the process to help get your contribution accepted.
+
+## Sign off Your Work
+
+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.
+
+```text
+This is my commit message
+
+Signed-off-by: Random J Developer <[email protected]>
+```
+
+See `git help commit`:
+
+```text
+-s, --signoff
+    Add Signed-off-by line by the committer at the end of the commit log
+    message. The meaning of a signoff depends on the project, but it typically
+    certifies that committer has the rights to submit this work under the same
+    license and agrees to a Developer Certificate of Origin (see
+    http://developercertificate.org/ for more information).
+```
+
+## How to Contribute
+
+1. Fork this repository, develop, and test your changes
+1. Remember to sign off your commits as described above
+1. Submit a pull request
+
+***NOTE***: In order to make testing and merging of PRs easier, please submit changes to multiple charts in separate PRs.
+
+### Technical Requirements
+
+* Must pass [DCO check](#sign-off-your-work)
+* Must follow [Charts best practices](https://helm.sh/docs/topics/chart_best_practices/)
+* Must pass CI jobs for linting and installing changed charts with the [chart-testing](https://github.com/helm/chart-testing) tool
+* Any change to a chart requires a version bump following [semver](https://semver.org/) principles. See [Immutability](#immutability) and [Versioning](#versioning) below
+
+Once changes have been merged, the release job will automatically run to package and release changed charts.
+
+### Immutability
+
+Chart releases must be immutable. Any change to a chart warrants a chart version bump even if it is only changed to the documentation.
+
+### Versioning
+
+The chart `version` should follow [semver](https://semver.org/).
+
+Charts should start at `1.0.0`. Any breaking (backwards incompatible) changes to a chart should:
+
+1. Bump the MAJOR version
+2. In the README, under a section called "Upgrading", describe the manual steps necessary to upgrade to the new (specified) MAJOR version
+
+### Community Requirements
+
+This project is released with a [Contributor Covenant](https://www.contributor-covenant.org).
+By participating in this project you agree to abide by its terms.
+See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).

README.md

@@ -0,0 +1,26 @@
+# Jenkins Community Kubernetes Helm Charts
+
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+This functionality is in beta and is subject to change. The code is provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
+
+## Usage
+
+[Helm](https://helm.sh) must be installed to use the charts.
+Please refer to Helm's [documentation](https://helm.sh/docs/) to get started.
+
+Once Helm is set up properly, add the repo as follows:
+
+```console
+helm repo add jenkinsci https://jenkinsci.github.io/helm-charts
+```
+
+You can then run `helm search repo jenkinsci` to see the charts.
+
+## Contributing
+
+We'd love to have you contribute! Please refer to our [contribution guidelines](CONTRIBUTING.md) for details.
+
+## License
+
+[Apache 2.0 License](./LICENSE).

charts/jenkins/CHANGELOG.md

@@ -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.
 
+## 2.6.0 First release in jenkinsci GitHub org
+
+Updated README for new location
+
 ## 2.5.2
 
 Fix as per JENKINS-47112

charts/jenkins/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: jenkins
 home: https://jenkins.io/
-version: 2.5.2
+version: 2.6.0
 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

charts/jenkins/README.md

@@ -13,12 +13,19 @@ This chart will do the following:
 * 1 x Jenkins Master with port 8080 exposed on an external LoadBalancer
 * All using Kubernetes Deployments
 
+## Get Repo Info
+
+```console
+helm repo add jenkinsci https://jenkinsci.github.io/helm-charts
+helm repo update
+```
+
 ## Installing the Chart
 
 To install the chart with the release name `my-release`:
 
 ```bash
-$ helm install my-release stable/jenkins
+$ helm install my-release jenkinsci/jenkins
 ```
 
 ## Upgrading an existing Release to a new major version
@@ -410,7 +417,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 my-release -f values.yaml stable/jenkins
+$ helm install my-release -f values.yaml jenkinsci/jenkins
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -442,7 +449,7 @@ the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ p
 
 Install helm chart with network policy enabled:
 
-    $ helm install stable/jenkins --set networkPolicy.enabled=true
+    $ helm install jenkinsci/jenkins --set networkPolicy.enabled=true
 
 You can use `master.networkPolicy.internalAgents` and `master.networkPolicy.externalAgents` stanzas to fine grained controls over where internal/external agents can connect from. Internal ones are allowed based on pod labels and (optionally) namespaces, and external ones are allowed based on IP ranges.
 
@@ -512,15 +519,15 @@ It is possible to mount several volumes using `persistence.volumes` and `persist
 3. Install the chart
 
 ```bash
-$ helm install my-release --set persistence.existingClaim=PVC_NAME stable/jenkins
+$ helm install my-release --set persistence.existingClaim=PVC_NAME jenkinsci/jenkins
 ```
 
 #### Storage Class
 
 It is possible to define which storage class to use:
 
 ```bash
-$ helm install my-release --set persistence.storageClass=customStorageClass stable/jenkins
+$ helm install my-release --set persistence.storageClass=customStorageClass jenkinsci/jenkins
 ```
 
 If set to a dash (`-`, as in `persistence.storageClass=-`), the dynamic provision is disabled.
@@ -566,7 +573,7 @@ rbac:
 
 RBAC is enabled by default if you want to disable it you will need to do the following:
 
-* `helm install stable/jenkins --set rbac.create=false`
+* `helm install jenkinsci/jenkins --set rbac.create=false`
 
 ## Backup