For deploying we should check if the artifactory has support for it https://www.jfrog.com/confluence/display/JFROG/Helm+Chart+Repository
Otherwise we can adapt my shared pipeline that deploys to GitHub pages https://github.com/halkeye/jenkins-shared-library/blob/master/vars/buildHelmChart.groovy On Mon., Aug. 24, 2020, 3:07 p.m. Torsten Walter, <m...@torstenwalter.de> wrote: > Hi Tim, > > thank you for approving the hosting request.That was really quick. I did > not expect that ;-) > > I removed my original repository as requested "Please remove your original > repository so that the jenkinsci repository is the definitive source for > the code.". GitHub now shows https://github.com/jenkinsci/helm-charts as > forked from slide/helm-chart <https://github.com/slide/helm-charts>. > > Is it possible to get https://github.com/apps/dco and > https://github.com/apps/stale installed to the new repository? Or could > you suggest an alternative for it? > > Regards > Torsten > > > timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2: > >> Hi Torsten >> >> We were just discussing this today on IRC strangely enough and I was >> planning to reach out to you about this. >> >> I take your point Gavin about there being issues with it but this helm >> chart has a lot of adoption and it’s best to improve what we have (and I’d >> be happy to help) >> >> The easiest way is for you to create a hosting request in Jenkins Jira, >> we can then fork it and you can delete your origin repo >> >> Thanks >> Tim >> >> On Mon, 24 Aug 2020 at 20:06, Torsten Walter <ma...@torstenwalter.de> >> wrote: >> >>> Hi together, >>> >>> Maybe some of you have used the stable/jenkins >>> <https://github.com/helm/charts/tree/master/stable/jenkins> helm chart >>> to install our favorite CI tool in Kubernetes. >>> >>> At the moment is it hosted in the https://github.com/helm/charts repository, >>> which is already in maintenance mode and all charts from there will be >>> de-listed from the Helm Hub. And on Nov 13, 2020 the support for that >>> repository will formally end, and the repo will be marked obsolete >>> >>> Therefor chart maintainers are currently moving charts to different >>> organizations. >>> >>> I am one of the maintainers of the stable/jenkins chart and I am >>> proposing to move it to https://github.com/jenkinsci. I find that to be >>> the most fitting place as most of the jenkins plugins also reside there. It >>> could help to continue supporting it in the future. >>> >>> Some data about the helm chart. Unfortunately, there seems to be no >>> usage statistics to tell how many people are using it or how many downloads >>> it has. >>> I checked its git history and noticed that it's first git commit is >>> already from September 2016 and that it received over 300 contributions >>> from 181 contributors since then. An older version of it is even used in >>> jenkins-x-platfrom >>> <https://github.com/jenkins-x/jenkins-x-platform/blob/f288b8ce107bb8bfc895d6827cf092266bdf9a00/jenkins-x-platform/requirements.yaml#L2-L5> >>> . >>> >>> How could a migration look like? Ideally, we could get a repository and >>> admin permission on it so that we could set everything up. I've seen >>> https://www.jenkins.io/doc/developer/publishing/requesting-hosting/, >>> but hosting a helm chart is a bit different than a Jenkins plugin. Also >>> with the recent discussion about forked repositories in GitHub I am not >>> sure if that's still the desired process or if it would be easier to just >>> move a repository to the new org. >>> >>> So far I prepared a git repository >>> https://github.com/torstenwalter/helm-charts which could either be >>> moved or forked into the jenkinci org. It contains the whole history of >>> the helm chart. It's using Apache License 2.0, as that was used by the >>> original repository. >>> CI is set up using chart-releaser >>> <https://github.com/helm/chart-releaser-action> and chart-testing >>> <https://github.com/helm/chart-testing-action> GitHub Actions. >>> >>> Let me know what you think of it and if a move to jenkinci GitHub org >>> would be ok. >>> >>> Best regards >>> >>> Torsten Walter >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> >>> >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-de...@googlegroups.com. >>> >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuushZREK__OT2Gj1pz96AB4ZHUz7WxERrt%2BNEECgkJLww%40mail.gmail.com.
