I can host > On Aug 24, 2020, at 1:32 PM, Oleg Nenashev <[email protected]> wrote: > > W.r.t a call, I suggest to do it under the umbrella of the Cloud Native SIG. > I won't be able to host meetings until Sep 18 at least, but I am perfectly > fine if someone else hosts the meeting. > Tim and Marky have permissions from those who replied in this thread. > > On Monday, August 24, 2020 at 10:25:48 PM UTC+2, Gavin Mogan wrote: > Agreed on all the xml > I think all the ssl stuff should go too, k8s has had ingress for a long time > now which handles it a lot better than jenkins does. > https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml#L226-L236 > > <https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml#L226-L236> > should probably get changed to a hash and use the plugin manager tool > (https://github.com/jenkinsci/plugin-installation-manager-tool > <https://github.com/jenkinsci/plugin-installation-manager-tool>) which should > be now in the docker image > everything slave should get renamed to agent as per the rename years ago > everything that uses jenkins ref directory should get fixed to use the > jenkins home directory. I think a lot of the hacks people have added have > been attempting to get around this > > On Mon, Aug 24, 2020 at 12:51 PM Torsten Walter <ma...@ <>torstenwalter.de > <http://torstenwalter.de/>> wrote: > Hi Tim, > > thanks for offering your help. I created a hosting request: > https://issues.jenkins-ci.org/browse/HOSTING-1015 > <https://issues.jenkins-ci.org/browse/HOSTING-1015> > > I also think that the chart could be improved. For example I'd like to get > rid of all the XML configuration options. They've been added at a time when > JCasC did not exist. With JCasC support now I would prefer to offer only a > single configuration option and configuration as code would be cleaner from > my point of view. I think keeping XML configuration made it easier for people > to do a transition, but removing them would make maintenance easier and also > help the user which option to choose. > > Regards > Torsten > > > [email protected] <> 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 <[email protected] <>> > 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 > <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 <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/ > <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 > <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 [email protected] <>. > > > 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 jenkin...@ <>googlegroups.com <http://googlegroups.com/>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%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 [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C374759B-3B08-45E2-8B00-81C6EE06A3FF%40gmail.com.
signature.asc
Description: Message signed with OpenPGP
