date:20200824

Count me in!

> On Aug 24, 2020, at 3:45 PM, Alyssa Tong  wrote:
> 
> 
> Hi All,
> 
> The Jenkins project, along with CDF will be at DevOps World's virtual event 
> this coming Sept 22-24, 2020. We are looking for Jenkins volunteers to help 
> staff the virtual booth, it is a 1 hour commitment in the comfort of your 
> home/office - of course we would not decline if you'd like to give more than 
> 1 hr ☺. Duties include answering Jenkins technical questions by attendee(s). 
> The signup sheet is  HERE.
> 
> If you have questions pls reach out.
> 
> Thank you,
> alyssa
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawdccTAKa4PrrhO62BJn9e5%2BToBVHvSors%3DbFR5kCePyQ%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9202AF94-C236-4CA3-8353-58B84397C302%40gmail.com.

[Event] DevOps World | Sept 22-24: Jenkins volunteers needed

2020-08-24 Thread Alyssa Tong

Hi All,

The Jenkins project, along with CDF  will be at DevOps
World's virtual event  this coming
Sept 22-24, 2020. We are looking for Jenkins volunteers to help staff the
virtual booth, it is a 1 hour commitment in the comfort of your home/office
- of course we would not decline if you'd like to give more than 1 hr ☺.
Duties include answering Jenkins technical questions by attendee(s). The
signup sheet is  HERE

.

If you have questions pls reach out.

Thank you,
alyssa

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawdccTAKa4PrrhO62BJn9e5%2BToBVHvSors%3DbFR5kCePyQ%40mail.gmail.com.

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

2020-08-24 Thread 'Gavin Mogan' via Jenkins Developers

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

https://www.jfrog.com/confluence/display/JFROG/Helm+Chart+Repository

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

https://github.com/halkeye/jenkins-shared-library/blob/master/vars/buildHelmChart.groovy

On Mon., Aug. 24, 2020, 3:07 p.m. Torsten Walter, 
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
>
>
> timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>
>> Hi Torsten
>>
>> We were just discussing this today on IRC strangely enough and I was
>> planning to reach out to you about this.
>>
>> I take your point Gavin about there being issues with it but this helm
>> chart has a lot of adoption and it’s best to improve what we have (and I’d
>> be happy to help)
>>
>> The easiest way is for you to create a hosting request in Jenkins Jira,
>> we can then fork it and you can delete your origin repo
>>
>> Thanks
>> Tim
>>
>> On Mon, 24 Aug 2020 at 20:06, Torsten Walter 
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To

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

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


timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:

> Hi Torsten
>
> We were just discussing this today on IRC strangely enough and I was 
> planning to reach out to you about this.
>
> I take your point Gavin about there being issues with it but this helm 
> chart has a lot of adoption and it’s best to improve what we have (and I’d 
> be happy to help)
>
> The easiest way is for you to create a hosting request in Jenkins Jira, we 
> can then fork it and you can delete your origin repo
>
> Thanks
> Tim
>
> On Mon, 24 Aug 2020 at 20:06, Torsten Walter  
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a407d2cf-b8eb-4283-aef7-71376df1bb62n%40googlegroups.com.

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

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  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,  > wrote:
> I can host
> 
>> On Aug 24, 2020, at 1:32 PM, Oleg Nenashev > > 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 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
>> 
>> 
>> timja...@gmail.com <> schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>> Hi Torsten
>> 
>> We were just discussing this today on IRC strangely enough and I was 
>> planning to reach out to you about this.
>> 
>> I take your point Gavin about there being issues with it but this helm chart 
>> has a lot of adoption and it’s best to improve what we have (and I’d be 
>> happy to help)
>> 
>> The easiest way is for you to create a hosting request in Jenkins Jira, we 
>> can then fork it and you can delete your origin repo
>> 
>> Thanks
>> Tim
>> 
>> On Mon, 24 Aug 2020 at 20:06, Torsten Walter > 
>> 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?

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

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,  wrote:

> I can host
>
> On Aug 24, 2020, at 1:32 PM, Oleg Nenashev  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 
>> 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
>>>
>>>
>>> timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>>>
 Hi Torsten

 We were just discussing this today on IRC strangely enough and I was
 planning to reach out to you about this.

 I take your point Gavin about there being issues with it but this helm
 chart has a lot of adoption and it’s best to improve what we have (and I’d
 be happy to help)

 The easiest way is for you to create a hosting request in Jenkins Jira,
 we can then fork it and you can delete your origin repo

 Thanks
 Tim

 On Mon, 24 Aug 2020 at 20:06, Torsten Walter 
 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

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

I can host

> On Aug 24, 2020, at 1:32 PM, Oleg Nenashev  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 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
> 
> 
> timja...@gmail.com <> schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
> Hi Torsten
> 
> We were just discussing this today on IRC strangely enough and I was planning 
> to reach out to you about this.
> 
> I take your point Gavin about there being issues with it but this helm chart 
> has a lot of adoption and it’s best to improve what we have (and I’d be happy 
> to help)
> 
> The easiest way is for you to create a hosting request in Jenkins Jira, we 
> can then fork it and you can delete your origin repo
> 
> Thanks
> Tim
> 
> On Mon, 24 Aug 2020 at 20:06, Torsten Walter > 
> 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

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

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  > 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
>>
>>
>> timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>>
>>> Hi Torsten
>>>
>>> We were just discussing this today on IRC strangely enough and I was 
>>> planning to reach out to you about this.
>>>
>>> I take your point Gavin about there being issues with it but this helm 
>>> chart has a lot of adoption and it’s best to improve what we have (and I’d 
>>> be happy to help)
>>>
>>> The easiest way is for you to create a hosting request in Jenkins Jira, 
>>> we can then fork it and you can delete your origin repo
>>>
>>> Thanks
>>> Tim
>>>
>>> On Mon, 24 Aug 2020 at 20:06, Torsten Walter  
>>> 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

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

2020-08-24 Thread 'Gavin Mogan' via Jenkins Developers

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 
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
>
>
> timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>
>> Hi Torsten
>>
>> We were just discussing this today on IRC strangely enough and I was
>> planning to reach out to you about this.
>>
>> I take your point Gavin about there being issues with it but this helm
>> chart has a lot of adoption and it’s best to improve what we have (and I’d
>> be happy to help)
>>
>> The easiest way is for you to create a hosting request in Jenkins Jira,
>> we can then fork it and you can delete your origin repo
>>
>> Thanks
>> Tim
>>
>> On Mon, 24 Aug 2020 at 20:06, Torsten Walter 
>> 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
>>>

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

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: 
> 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
>
>
> timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:
>
>> Hi Torsten
>>
>> We were just discussing this today on IRC strangely enough and I was 
>> planning to reach out to you about this.
>>
>> I take your point Gavin about there being issues with it but this helm 
>> chart has a lot of adoption and it’s best to improve what we have (and I’d 
>> be happy to help)
>>
>> The easiest way is for you to create a hosting request in Jenkins Jira, 
>> we can then fork it and you can delete your origin repo
>>
>> Thanks
>> Tim
>>
>> On Mon, 24 Aug 2020 at 20:06, Torsten Walter  
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit

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

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


timja...@gmail.com schrieb am Montag, 24. August 2020 um 21:39:55 UTC+2:

> Hi Torsten
>
> We were just discussing this today on IRC strangely enough and I was 
> planning to reach out to you about this.
>
> I take your point Gavin about there being issues with it but this helm 
> chart has a lot of adoption and it’s best to improve what we have (and I’d 
> be happy to help)
>
> The easiest way is for you to create a hosting request in Jenkins Jira, we 
> can then fork it and you can delete your origin repo
>
> Thanks
> Tim
>
> On Mon, 24 Aug 2020 at 20:06, Torsten Walter  
> 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 jenkinsci-dev+unsubscr...@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.

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

I am happy to join a call to see if we can address your issues.

ga...@gavinmogan.com 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  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  
>> 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
>> .
>>
>>
>>
>> -- 
>> 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 jenkinsci-de...@googlegroups.com.
>>
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/32fe9e6f-70fc-4244-98cb-ab3cf948c381n%40googlegroups.com.

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

2020-08-24 Thread Tim Jacomb

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  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-dev+unsubscr...@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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifVV1CSsjWWctEeBGrv8cqneGi1ivxeFhqV-aGK8CEfdA%40mail.gmail.com.

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

I can help with this.

{ 
"regards" : {
 "name" : “marky”,
 "phone" : "+1 (408) 464 2965”,
 "email" : “marky.r.jack...@gmail.com",
 "team" : “jackson5“,
 “role” : “software engineer"
 }
 }

> On Aug 24, 2020, at 12:30 PM, 'Gavin Mogan' via Jenkins Infrastructure 
>  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  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  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-dev+unsubscr...@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.
>> 
>> 
>> 
>> -- 
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkins-infra+unsubscr...@googlegroups.com.
> 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

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

2020-08-24 Thread 'Gavin Mogan' via Jenkins Developers

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  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 
> 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-dev+unsubscr...@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
> .
>
>
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duswqk66igJ5z60JsibmwP2Qo8zk0TTrPvyWJKHhr-OqGw%40mail.gmail.com.

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

2020-08-24 Thread 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  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-dev+unsubscr...@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.



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

Move stable/jenkins kubernetes chart to jenkinci GitHub org

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-dev+unsubscr...@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.

Re: Limited availability until October - Oleg Nenashev

Count me in!

> On Aug 24, 2020, at 11:29 AM, Mark Waite  wrote:
> 
> Thanks for your willingness to help!
> 
> The advocacy SIG seems like the preferred first location, Marky.  Having 
> someone watch the social media sources, propose reposts and new entries, and 
> assist with sharing would be great.
> 
> If you're available to assist with Google Season of Docs mentoring, that  
> would also be a great help.  We'll be discussing more detailed plans for 
> Google Season of Docs at the Jenkins Docs SIG meeting this Friday.
> 
> Copy editing and review of posts to jenkins.io  would be 
> next on my list.  We have a number of proposed changes that need additional 
> review and editing before they are merged.
> 
> Thanks,
> Mark Waite
> 
> On Mon, Aug 24, 2020 at 12:22 PM Marky Jackson  > wrote:
> Oleg,
> Breaks are good and I can attest to it.
> With that being said, I am fresh and ready to jump back in. Mark Waite, 
> please let me know where I can help.
> 
> On Saturday, August 22, 2020 at 2:22:03 PM UTC-7 Oleg Nenashev wrote:
> Dear all,
> 
> Due to the long-anticipated vacation in September and some other changes in 
> my responsibilities, I will have a very limited bandwidth in the Jenkins 
> community until October. I would like to set an expectation that I will be 
> unable to dedicate as much time as before to the community and the project. 
> My responses in mailing lists and chats will be also delayed, especially in 
> the period of Aug 31..Sep 17. Will be back in October.
> 
> I will keep doing GSoC mentorship and org administration, GSoD and some 
> governance bits like the 2020 elections prepwork we discussed at the previous 
> governance meeting. I will keep maintaining Jenkinsfile Runner, as much as my 
> time allows. I will also run a Jenkins Roadmap meeting next week so that we 
> keep the process moving forward.
> 
> I will temporarily put on hold other roles. Most notable ones: Jenkins core 
> maintenance, jenkins.io  copy editing, running SIGs and 
> online meetups, social media content management, permission management, 
> infra, etc. As far as I can tell, I am not a single-person bottleneck in any 
> of these roles. Thanks a lot to all contributors who work on these areas! 
> Should there be a permission issue (e.g. plugin release permissions or any 
> service access), I grant a blanket approval to governance board members Alex 
> Earl and Ulli Hafner to transfer my permissions to other contributors if 
> needed. Similarly, I grant a blanket approval to Daniel Beck to transfer my 
> permissions in the case of Security Team needs. All these contributors will 
> have my emergency contacts, just in case.
> 
> If you see any areas with a bus factor of one and/or would like to get 
> permissions, please respond to this thread.
> 
> Best regards,
> Oleg Nenashev
> 
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/32d349a0-4336-401b-aa7a-f0e5c58316e7n%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 jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG_0YZYSxwN3yNBCK7MfL85gJ%3DfK%2Bk%2BxdN6fVN6T2UCtw%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/759CDCB3-07D3-471D-9A4E-F5C2225AAA9F%40gmail.com.


signature.asc
Description: Message signed with OpenPGP

Re: Limited availability until October - Oleg Nenashev

2020-08-24 Thread Mark Waite

Thanks for your willingness to help!

The advocacy SIG seems like the preferred first location, Marky.  Having
someone watch the social media sources, propose reposts and new entries,
and assist with sharing would be great.

If you're available to assist with Google Season of Docs mentoring, that
would also be a great help.  We'll be discussing more detailed plans for
Google Season of Docs at the Jenkins Docs SIG meeting this Friday.

Copy editing and review of posts to jenkins.io would be next on my list.
We have a number of proposed changes that need additional review and
editing before they are merged.

Thanks,
Mark Waite

On Mon, Aug 24, 2020 at 12:22 PM Marky Jackson 
wrote:

> Oleg,
> Breaks are good and I can attest to it.
> With that being said, I am fresh and ready to jump back in. Mark Waite,
> please let me know where I can help.
>
> On Saturday, August 22, 2020 at 2:22:03 PM UTC-7 Oleg Nenashev wrote:
>
>> Dear all,
>>
>> Due to the long-anticipated vacation in September and some other changes
>> in my responsibilities, I will have a very limited bandwidth in the Jenkins
>> community until October. I would like to set an expectation that I will be
>> unable to dedicate as much time as before to the community and the project.
>> My responses in mailing lists and chats will be also delayed, especially in
>> the period of Aug 31..Sep 17. Will be back in October.
>>
>> I will keep doing GSoC mentorship and org administration, GSoD and some
>> governance bits like the 2020 elections prepwork we discussed at the
>> previous governance meeting. I will keep maintaining Jenkinsfile Runner, as
>> much as my time allows. I will also run a Jenkins Roadmap meeting next week
>> so that we keep the process moving forward.
>>
>> I will temporarily put on hold other roles. Most notable ones: Jenkins
>> core maintenance, jenkins.io copy editing, running SIGs and online
>> meetups, social media content management, permission management, infra,
>> etc. As far as I can tell, I am not a single-person bottleneck in any of
>> these roles. Thanks a lot to all contributors who work on these areas!
>> Should there be a permission issue (e.g. plugin release permissions or any
>> service access), I grant a blanket approval to governance board members
>> Alex Earl and Ulli Hafner to transfer my permissions to other contributors
>> if needed. Similarly, I grant a blanket approval to Daniel Beck to transfer
>> my permissions in the case of Security Team needs. All these contributors
>> will have my emergency contacts, just in case.
>>
>> If you see any areas with a bus factor of one and/or would like to get
>> permissions, please respond to this thread.
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/32d349a0-4336-401b-aa7a-f0e5c58316e7n%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG_0YZYSxwN3yNBCK7MfL85gJ%3DfK%2Bk%2BxdN6fVN6T2UCtw%40mail.gmail.com.

Re: Limited availability until October - Oleg Nenashev

Oleg,
Breaks are good and I can attest to it.
With that being said, I am fresh and ready to jump back in. Mark Waite, 
please let me know where I can help. 

On Saturday, August 22, 2020 at 2:22:03 PM UTC-7 Oleg Nenashev wrote:

> Dear all,
>
> Due to the long-anticipated vacation in September and some other changes 
> in my responsibilities, I will have a very limited bandwidth in the Jenkins 
> community until October. I would like to set an expectation that I will be 
> unable to dedicate as much time as before to the community and the project. 
> My responses in mailing lists and chats will be also delayed, especially in 
> the period of Aug 31..Sep 17. Will be back in October.
>
> I will keep doing GSoC mentorship and org administration, GSoD and some 
> governance bits like the 2020 elections prepwork we discussed at the 
> previous governance meeting. I will keep maintaining Jenkinsfile Runner, as 
> much as my time allows. I will also run a Jenkins Roadmap meeting next week 
> so that we keep the process moving forward.
>
> I will temporarily put on hold other roles. Most notable ones: Jenkins 
> core maintenance, jenkins.io copy editing, running SIGs and online 
> meetups, social media content management, permission management, infra, 
> etc. As far as I can tell, I am not a single-person bottleneck in any of 
> these roles. Thanks a lot to all contributors who work on these areas! 
> Should there be a permission issue (e.g. plugin release permissions or any 
> service access), I grant a blanket approval to governance board members 
> Alex Earl and Ulli Hafner to transfer my permissions to other contributors 
> if needed. Similarly, I grant a blanket approval to Daniel Beck to transfer 
> my permissions in the case of Security Team needs. All these contributors 
> will have my emergency contacts, just in case.
>
> If you see any areas with a bus factor of one and/or would like to get 
> permissions, please respond to this thread.
>
> Best regards,
> Oleg Nenashev
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/32d349a0-4336-401b-aa7a-f0e5c58316e7n%40googlegroups.com.

Re: JEP-224 and ExtendedRead - Time to graduate to GA?

+1 from me as a BDFL delegate in this story.
I believe that the community process has been followed, and that all 
necessary quality gates have been passed.
If there is no negative feedback, I plan to merge the pull request and mark 
the pull request as accepted

Best regards,
Oleg

On Friday, August 14, 2020 at 1:24:22 PM UTC+2, Antonio Muñiz wrote:
>
> +1
>
> On Thu, 13 Aug 2020 at 22:59, Tim Jacomb > 
> wrote:
>
>> Minor correction matrix auth doesn't depend on the plugin and role 
>> strategy will no longer depend on it after 
>> https://github.com/jenkinsci/role-strategy-plugin/pull/139 is merged
>> (Both have a minimum core of 2.222.x)
>>
>> On Thu, 13 Aug 2020 at 21:46, Tim Jacomb > > wrote:
>>
>>> Hi all
>>>
>>> Thoughts on graduating to GA:
>>>
>>>- Agent/ExtendedRead
>>>- Job/ExtendedRead
>>>- Overall/SystemRead
>>>
>>> GA would mean:
>>>
>>>- Enabled by default
>>>- Beta API restriction removed from Overall/SystemRead
>>>- Only weekly line affected for now, wouldn't be GA in LTS until the 
>>>line after 2.249
>>>
>>> Note: enabling by default doesn't make a huge practical difference as 
>>> the extended-read-permission plugin is depended on by role strategy and 
>>> matrix-auth and installing that plugin enabled the permission, which means 
>>> that any updated instance has had this automatically enabled, as can be 
>>> seen in this graph 
>>> :
>>>
>>> [image: image.png]
>>>
>>> Background:
>>>
>>> Job/ExtendedRead was introduced into Jenkins in 2009 
>>> ,
>>>  
>>> and has seen many plugins adopt it over the years, but was disabled by 
>>> default to gather feedback and because of a concern over the permissions 
>>> matrix getting too wide.
>>>
>>> Agent/ExtendedRead was introduced in 2013 
>>> ,
>>>  
>>> but didn't see much adoption as it was only added for the REST API in core, 
>>> undocumented and the extended-read-permission plugin didn't enable it like 
>>> it did for jobs. This was fixed in 2.238 
>>> , with access being extended 
>>> to all agent views.
>>>
>>> Overall/SystemRead was introduced in 2.222 
>>>  as part of JEP-224 
>>> , it added onto the initial 
>>> Job/ExtendedRead by extending the jelly controls to have a read only 
>>> appearance, replacing text boxes with text, and disabling controls like 
>>> radio buttons and checkboxes. Initially it was just used on the System 
>>> configuration page, but many patches 
>>>  were landed up till 2.239 
>>>  to cover most of Jenkins 
>>> core. Additionally Cloud Stats, JCasC, Simple Disk Usage, Matrix Auth and 
>>> Role Strategy plugins have been updated.
>>>
>>> I've created draft PRs for updating the status of the JEP 
>>>  and Jenkins core 
>>> pending feedback.
>>>
>>> Thoughts +1, -1, ±0?
>>>
>>> Thanks
>>> Tim
>>>
>>>
>>> -- 
>> 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/CAH-3BicOv%2BBkYtxFsoGyyE%2Bsiz6esxppp9_A%3DDdr-%3DejFzCnZw%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> Antonio Muñiz
> Human, Engineer
> CloudBees, Inc.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2ab1b041-728b-4a11-82ae-5a3427583f90o%40googlegroups.com.

Re: Backporting for 2.249.1?