-
Notifications
You must be signed in to change notification settings - Fork 16.7k
[stable/jenkins] Migration to new location #23562
Comments
As we discussed happy to collaborate as well just ping me 😄 |
@lachie83 @viglesiasce @maorfr @mogaal @wmcdona89 I create a temporary repository for the Jenkins chart similar to what @scottrigby did for prometheus. For this I cloned this repository and filtered only jenkins chart itself.
CI pipeline is using GitHub actions: You can test it via:
Next I'll invite you as collaborator and start a discussion in the Jenkins community if it's possible to get a repository in https://github.com/jenkinsci GitHub org. I'd love to get your feedback on https://github.com/torstenwalter/helm-charts/pull/1, where I added a README and contributing guidelines. For the code of conduct I pointed to Jenkins Code of Conduct. |
Hosting request was approved and the repository is now hosted in https://github.com/jenkinsci/helm-charts/. I will delete https://github.com/torstenwalter/helm-charts and create PR in the new location. |
As we now have a new repository we can track tasks which are required to do the migration in there https://github.com/jenkinsci/helm-charts/projects/2 |
Quote from #21103 as it provides the context:
I propose to also move the
stable/jenkins
chart to a new location. From a context perspective it would be great if we could move it to https://github.com/jenkinsci, which also hosts the majority of Jenkins plugins. That would make it easier for people to find it and it could also encourage contributions from the community.As far as I can tell there is no Jenkins chart. There is however a kubernetes-operator, which provides similar functionality.
A Kubernetes operator can offer more functionality than a plain helm chart on the other hand installing an operator requires more privileges within a cluster which can make it hard to use in certain environments.
For migrating the chart I suggest the following
The text was updated successfully, but these errors were encountered: