Move stable/jenkins kubernetes chart to jenkinci GitHub org

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Matt Sicker
Based on repositories like https://github.com/jenkinsci/docker and
https://github.com/jenkinsci/kubernetes-operator I'd imagine that
jenkinsci is the perfect organization for this!

On Mon, Aug 24, 2020 at 2:06 PM Torsten Walter <[hidden email]> wrote:

>
> Hi together,
>
> Maybe some of you have used the 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.
>
> 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 and chart-testing 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozRDfxBdjf%3Di6UGC6aHsXfKomb2GbnQmKVh_GbJJbH%3Dmw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Gavin Mogan
We've been fighting with the helm chart in #jenkins-infra all weekend.

Its a horrendous mess full of hacks by people who barely understand jenkins let alone k8s and helm.
Like for example, all plugins are downloaded every time, and thrown in a saved PVC, but never retrieved from there.
They are also saved into the jenkins ref directory, which is copied without overwriting into your install. Which means if it downloads a newer version of a plugin, it won't overwrite it.

I think it's worth making an official helm chart, but I don't think we should base it on the "helm/stable" one, maybe just take some of the useful features.

On Mon, Aug 24, 2020 at 12:18 PM Matt Sicker <[hidden email]> wrote:
Based on repositories like https://github.com/jenkinsci/docker and
https://github.com/jenkinsci/kubernetes-operator I'd imagine that
jenkinsci is the perfect organization for this!

On Mon, Aug 24, 2020 at 2:06 PM Torsten Walter <[hidden email]> wrote:
>
> Hi together,
>
> Maybe some of you have used the 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.
>
> 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 and chart-testing 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozRDfxBdjf%3Di6UGC6aHsXfKomb2GbnQmKVh_GbJJbH%3Dmw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duswqk66igJ5z60JsibmwP2Qo8zk0TTrPvyWJKHhr-OqGw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: [jenkins-infra] Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Marky Jackson
I can help with this.

{     
    "regards" : {
         "name" : “marky”,
         "phone" : "<a href="tel:+1%20(408)%20464%202965" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="0">+1 (408) 464 2965”,
         "email" : “[hidden email]",
         "team" : “jackson5“,
 “role” : “software engineer"
     }
 }

On Aug 24, 2020, at 12:30 PM, 'Gavin Mogan' via Jenkins Infrastructure <[hidden email]> wrote:


We've been fighting with the helm chart in #jenkins-infra all weekend.

Its a horrendous mess full of hacks by people who barely understand jenkins let alone k8s and helm.
Like for example, all plugins are downloaded every time, and thrown in a saved PVC, but never retrieved from there.
They are also saved into the jenkins ref directory, which is copied without overwriting into your install. Which means if it downloads a newer version of a plugin, it won't overwrite it.

I think it's worth making an official helm chart, but I don't think we should base it on the "helm/stable" one, maybe just take some of the useful features.

On Mon, Aug 24, 2020 at 12:18 PM Matt Sicker <[hidden email]> wrote:
Based on repositories like https://github.com/jenkinsci/docker and
https://github.com/jenkinsci/kubernetes-operator I'd imagine that
jenkinsci is the perfect organization for this!

On Mon, Aug 24, 2020 at 2:06 PM Torsten Walter <[hidden email]> wrote:
>
> Hi together,
>
> Maybe some of you have used the 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.
>
> 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 and chart-testing 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozRDfxBdjf%3Di6UGC6aHsXfKomb2GbnQmKVh_GbJJbH%3Dmw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/CAG%3D_Duswqk66igJ5z60JsibmwP2Qo8zk0TTrPvyWJKHhr-OqGw%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/BA22F053-7403-441A-818E-0AE6B0937A0D%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Tim Jacomb
In reply to this post by Torsten Walter
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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.




--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifVV1CSsjWWctEeBGrv8cqneGi1ivxeFhqV-aGK8CEfdA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
In reply to this post by Gavin Mogan
I am happy to join a call to see if we can address your issues.

[hidden email] schrieb am Montag, 24. August 2020 um 21:30:25 UTC+2:
We've been fighting with the helm chart in #jenkins-infra all weekend.

Its a horrendous mess full of hacks by people who barely understand jenkins let alone k8s and helm.
Like for example, all plugins are downloaded every time, and thrown in a saved PVC, but never retrieved from there.
They are also saved into the jenkins ref directory, which is copied without overwriting into your install. Which means if it downloads a newer version of a plugin, it won't overwrite it.

I think it's worth making an official helm chart, but I don't think we should base it on the "helm/stable" one, maybe just take some of the useful features.

On Mon, Aug 24, 2020 at 12:18 PM Matt Sicker <[hidden email]> wrote:
Based on repositories like https://github.com/jenkinsci/docker and
https://github.com/jenkinsci/kubernetes-operator I'd imagine that
jenkinsci is the perfect organization for this!

On Mon, Aug 24, 2020 at 2:06 PM Torsten Walter <[hidden email]> wrote:
>
> Hi together,
>
> Maybe some of you have used the 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.
>
> 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 and chart-testing 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/32fe9e6f-70fc-4244-98cb-ab3cf948c381n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
In reply to this post by Tim Jacomb
Hi Tim,

thanks for offering your help. I created a hosting request: 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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Oleg Nenashev
As discussed in another channel, I am +1 for hosting.
Thanks for starting the thread, Torsten!

Best regards,
Oleg

On Monday, August 24, 2020 at 9:50:45 PM UTC+2, Torsten Walter wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: <a href="https://issues.jenkins-ci.org/browse/HOSTING-1015" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FHOSTING-1015\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFouY-F-2c6698iczohyKmEuYym7g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FHOSTING-1015\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFouY-F-2c6698iczohyKmEuYym7g&#39;;return true;">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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the <a href="https://github.com/helm/charts/tree/master/stable/jenkins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Ftree%2Fmaster%2Fstable%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy4VIloaURtmk1hR6CXXZlGl50Zw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Ftree%2Fmaster%2Fstable%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy4VIloaURtmk1hR6CXXZlGl50Zw&#39;;return true;">stable/jenkins helm chart to install our favorite CI tool in Kubernetes. 

At the moment is it hosted in the <a href="https://github.com/helm/charts" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGRK4svdDrNiUMgbyydGYMbxTjVtQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGRK4svdDrNiUMgbyydGYMbxTjVtQ&#39;;return true;">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 <a href="https://github.com/jenkinsci" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgLFBS-sCs7AgyJ7zbYqH_H8xk4g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgLFBS-sCs7AgyJ7zbYqH_H8xk4g&#39;;return true;">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 <a href="https://github.com/jenkins-x/jenkins-x-platform/blob/f288b8ce107bb8bfc895d6827cf092266bdf9a00/jenkins-x-platform/requirements.yaml#L2-L5" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjenkins-x-platform%2Fblob%2Ff288b8ce107bb8bfc895d6827cf092266bdf9a00%2Fjenkins-x-platform%2Frequirements.yaml%23L2-L5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFm-v7D4UgTuR5tW_OmYjPFecLMZA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjenkins-x-platform%2Fblob%2Ff288b8ce107bb8bfc895d6827cf092266bdf9a00%2Fjenkins-x-platform%2Frequirements.yaml%23L2-L5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFm-v7D4UgTuR5tW_OmYjPFecLMZA&#39;;return true;">jenkins-x-platfrom.

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 <a href="https://www.jenkins.io/doc/developer/publishing/requesting-hosting/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Frequesting-hosting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH2G87K-4phjVlz66uW14qOXiRJxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Frequesting-hosting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH2G87K-4phjVlz66uW14qOXiRJxA&#39;;return true;">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 <a href="https://github.com/torstenwalter/helm-charts" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftorstenwalter%2Fhelm-charts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG_mYho308c4maOhTioRhDQYlx9mg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftorstenwalter%2Fhelm-charts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG_mYho308c4maOhTioRhDQYlx9mg&#39;;return true;">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 <a href="https://github.com/helm/chart-releaser-action" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-releaser-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGlZco-UnH5ZvGng2xox8AsIpCJKg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-releaser-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGlZco-UnH5ZvGng2xox8AsIpCJKg&#39;;return true;">chart-releaser and <a href="https://github.com/helm/chart-testing-action" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-testing-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHMelw3aZ8_8FZNPMPgBc1WTFCkHA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-testing-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHMelw3aZ8_8FZNPMPgBc1WTFCkHA&#39;;return true;">chart-testing 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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9ad24e81-96c7-4b99-a327-9050b6cb0a8do%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Gavin Mogan
In reply to this post by Torsten Walter
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 should probably get changed to a hash and use the plugin 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 <[hidden email]> wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: 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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuszCh4Xu1sTLE_9ae%3D%3DkyJ861QTMYjDMkN4QgWViorK1A%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Oleg Nenashev
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.
<a href="https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml#L226-L236" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Fblob%2Fmaster%2Fstable%2Fjenkins%2Fvalues.yaml%23L226-L236\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEsJ0jIfKngoQEeOzYLzi5yUkCpgg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Fblob%2Fmaster%2Fstable%2Fjenkins%2Fvalues.yaml%23L226-L236\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEsJ0jIfKngoQEeOzYLzi5yUkCpgg&#39;;return true;">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 (<a href="https://github.com/jenkinsci/plugin-installation-manager-tool" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fplugin-installation-manager-tool\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFwLvQnXQrdvZZ2jx8h9oRhIsSJEA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fplugin-installation-manager-tool\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFwLvQnXQrdvZZ2jx8h9oRhIsSJEA&#39;;return true;">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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="8DOQA0JEBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ma...@...> wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: <a href="https://issues.jenkins-ci.org/browse/HOSTING-1015" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FHOSTING-1015\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFouY-F-2c6698iczohyKmEuYym7g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FHOSTING-1015\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFouY-F-2c6698iczohyKmEuYym7g&#39;;return true;">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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the <a href="https://github.com/helm/charts/tree/master/stable/jenkins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Ftree%2Fmaster%2Fstable%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy4VIloaURtmk1hR6CXXZlGl50Zw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts%2Ftree%2Fmaster%2Fstable%2Fjenkins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy4VIloaURtmk1hR6CXXZlGl50Zw&#39;;return true;">stable/jenkins helm chart to install our favorite CI tool in Kubernetes. 

At the moment is it hosted in the <a href="https://github.com/helm/charts" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGRK4svdDrNiUMgbyydGYMbxTjVtQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fcharts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGRK4svdDrNiUMgbyydGYMbxTjVtQ&#39;;return true;">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 <a href="https://github.com/jenkinsci" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgLFBS-sCs7AgyJ7zbYqH_H8xk4g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgLFBS-sCs7AgyJ7zbYqH_H8xk4g&#39;;return true;">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 <a href="https://github.com/jenkins-x/jenkins-x-platform/blob/f288b8ce107bb8bfc895d6827cf092266bdf9a00/jenkins-x-platform/requirements.yaml#L2-L5" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjenkins-x-platform%2Fblob%2Ff288b8ce107bb8bfc895d6827cf092266bdf9a00%2Fjenkins-x-platform%2Frequirements.yaml%23L2-L5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFm-v7D4UgTuR5tW_OmYjPFecLMZA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-x%2Fjenkins-x-platform%2Fblob%2Ff288b8ce107bb8bfc895d6827cf092266bdf9a00%2Fjenkins-x-platform%2Frequirements.yaml%23L2-L5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFm-v7D4UgTuR5tW_OmYjPFecLMZA&#39;;return true;">jenkins-x-platfrom.

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 <a href="https://www.jenkins.io/doc/developer/publishing/requesting-hosting/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Frequesting-hosting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH2G87K-4phjVlz66uW14qOXiRJxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Frequesting-hosting%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH2G87K-4phjVlz66uW14qOXiRJxA&#39;;return true;">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 <a href="https://github.com/torstenwalter/helm-charts" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftorstenwalter%2Fhelm-charts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG_mYho308c4maOhTioRhDQYlx9mg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftorstenwalter%2Fhelm-charts\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG_mYho308c4maOhTioRhDQYlx9mg&#39;;return true;">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 <a href="https://github.com/helm/chart-releaser-action" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-releaser-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGlZco-UnH5ZvGng2xox8AsIpCJKg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-releaser-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGlZco-UnH5ZvGng2xox8AsIpCJKg&#39;;return true;">chart-releaser and <a href="https://github.com/helm/chart-testing-action" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-testing-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHMelw3aZ8_8FZNPMPgBc1WTFCkHA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fhelm%2Fchart-testing-action\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHMelw3aZ8_8FZNPMPgBc1WTFCkHA&#39;;return true;">chart-testing 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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="8DOQA0JEBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Marky Jackson
I can host

On Aug 24, 2020, at 1:32 PM, Oleg Nenashev <[hidden email]> 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 should probably get changed to a hash and use the plugin 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> wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: 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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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.



-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%40googlegroups.com.

--
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 [hidden email].
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 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
Cool! I could try to prepare some slides. Like Kubernetes manifests used, functionality and some reasoning behind it (at least what I know). We could also add enhancement suggestions like discussed in this thread. Thank you for the feedback this will help making it better.

@Marky could you create a dummy presentation e.g. Goggle Slides or whatever you normally use for meetings? I could then start to prepare something.



On Mon, 24 Aug 2020, 22:51 Marky Jackson, <[hidden email]> wrote:
I can host

On Aug 24, 2020, at 1:32 PM, Oleg Nenashev <[hidden email]> 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 should probably get changed to a hash and use the plugin 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> wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: 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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C374759B-3B08-45E2-8B00-81C6EE06A3FF%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAETayJOKV3A71KBYGPuGnGt4M89V_uwXk1bL3WALaqNpzxoBkQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Marky Jackson
I sent you a separate email with a link to a slide deck you can use.

On Aug 24, 2020, at 1:59 PM, Torsten Walter <[hidden email]> wrote:

Cool! I could try to prepare some slides. Like Kubernetes manifests used, functionality and some reasoning behind it (at least what I know). We could also add enhancement suggestions like discussed in this thread. Thank you for the feedback this will help making it better.

@Marky could you create a dummy presentation e.g. Goggle Slides or whatever you normally use for meetings? I could then start to prepare something.



On Mon, 24 Aug 2020, 22:51 Marky Jackson, <[hidden email]> wrote:
I can host

On Aug 24, 2020, at 1:32 PM, Oleg Nenashev <[hidden email]> 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 should probably get changed to a hash and use the plugin 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> wrote:
Hi Tim,

thanks for offering your help. I created a hosting request: 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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.



-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8667e02-e186-4b57-8fab-8c310bd2e984n%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/058b5dc9-3347-48ed-8db3-8fb438254cf9o%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C374759B-3B08-45E2-8B00-81C6EE06A3FF%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAETayJOKV3A71KBYGPuGnGt4M89V_uwXk1bL3WALaqNpzxoBkQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/DB207267-2478-42D7-B420-E841CEA9EBA5%40gmail.com.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
In reply to this post by Tim Jacomb
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.

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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Gavin Mogan
For deploying we should check if the artifactory has support for it 


Otherwise we can adapt my shared pipeline that deploys to GitHub pages


On Mon., Aug. 24, 2020, 3:07 p.m. Torsten Walter, <[hidden email]> 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.

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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuushZREK__OT2Gj1pz96AB4ZHUz7WxERrt%2BNEECgkJLww%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Tim Jacomb
Issues are open now, I've raised a few, [hidden email] (or anyone else) your feedback here would be greatly appreciated


On Mon, 24 Aug 2020 at 23:39, 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:
For deploying we should check if the artifactory has support for it 


Otherwise we can adapt my shared pipeline that deploys to GitHub pages


On Mon., Aug. 24, 2020, 3:07 p.m. Torsten Walter, <[hidden email]> 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.

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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuushZREK__OT2Gj1pz96AB4ZHUz7WxERrt%2BNEECgkJLww%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifQjXdp7kUY46tyVE%2BOAoaYbJ7oVv-Our2wmVosH%3DEWvw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Move stable/jenkins kubernetes chart to jenkinci GitHub org

Torsten Walter
I just wanted to let you know that the migration is completed and the first version was released from https://github.com/jenkinsci/helm-charts. The chart can be downloaded from https://charts.jenkins.io/.
The repository is set up in a way that it can host multiple charts. So for example the chart which installs the kubernetes-operator could also be hosted there. Looking forward to contributions from the community.

Thanks a lot to everyone who helped making this happen!

Best regards
Torsten 

[hidden email] schrieb am Mittwoch, 26. August 2020 um 13:23:01 UTC+2:
Issues are open now, I've raised a few, @Gavin Mogan (or anyone else) your feedback here would be greatly appreciated


On Mon, 24 Aug 2020 at 23:39, 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:
For deploying we should check if the artifactory has support for it 


Otherwise we can adapt my shared pipeline that deploys to GitHub pages


On Mon., Aug. 24, 2020, 3:07 p.m. Torsten Walter, <[hidden email]> 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.

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


[hidden email] 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 <[hidden email]> wrote:
Hi together,

Maybe some of you have used the 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.

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 and chart-testing 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 [hidden email].


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3f16a090-727d-42db-bbce-f39b11944477n%40googlegroups.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com.

--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/23f7a51b-e966-4b82-9506-4672c323c204n%40googlegroups.com.