Re: Using JDK 11 instead of JDK 8 in default docker images

[Raihaan Shouhell]

Perhaps removal of java 8 support should come with a bump in major version
number so jenkins 3.x and an announcement ahead of time.

Cheers,
Raihaan

On Wed, Apr 28, 2021, 7:42 AM Oleg Nenashev  wrote:

> I am in favor of making JDK11 the default in all our distributions,
> including controller and agent Docker images.
> At the same time I am afraid that removal of Java 1.8 support is
> premature. The vast majority of Jenkins users still uses this version, and
> the migration to Java 11 won't be seamless in al l cases. For example,
> Maven Plugin will effectively switch project builds to Java 11 once the
> agent images are updated. It will cause unexpected issues in user builds
> here and there. Nothing should be critical, but we should not force users
> to migrate immediately.
>
> IMHO there should be a grace period between Java 8 support deprecation and
> the actual removal. Maybe 6 months or so.
>
> BR, Oleg
>
> On Tuesday, April 27, 2021 at 7:13:17 PM UTC+2 slide wrote:
>
>> I agree with dropping java 8. There are some nice features in 11 that
>> would be good to use.
>>
>> On Tue, Apr 27, 2021 at 9:11 AM Tim Jacomb  wrote:
>>
>>> We’ve been using it for over a year on java 11 and never hit an issue...
>>>
>>> I would rather drop java 8 as well
>>>
>>> On Tue, 27 Apr 2021 at 15:48, Jesse Glick  wrote:
>>>
 My opinion remains that if we believe Java 11 support is solid enough
 to be the default, then we may as well keep things simple and drop Java 8
 support: start building core and important plugins with `java.level=11`,
 and take advantage of its features. Building and testing primarily against
 8 while pushing users to run 11, and forcing developers to consider both
 platforms in every situation, seems like the worst decision.

 --
 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/CANfRfr2hjuPWgK7XqzwezcT8eP1i1_ZZd_iMNreg%3D7K7FTzH8Q%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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifVe04fx-7vx6Dp-jkLmTvepCDGHXqRDLEWdHyNN8TG%3Dw%40mail.gmail.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Website: http://earl-of-code.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/74c9f96d-1acc-4315-9fd5-e59bb6fdeff8n%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/CAFoxvgwycdrsK9dX-A7KVcA%2Bi%3Dta6dhc4iZbVAz%2BRKv3dn5Ymg%40mail.gmail.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

[Oleg Nenashev]

I am in favor of making JDK11 the default in all our distributions, 
including controller and agent Docker images.
At the same time I am afraid that removal of Java 1.8 support is premature. 
The vast majority of Jenkins users still uses this version, and the 
migration to Java 11 won't be seamless in al l cases. For example, Maven 
Plugin will effectively switch project builds to Java 11 once the agent 
images are updated. It will cause unexpected issues in user builds here and 
there. Nothing should be critical, but we should not force users to migrate 
immediately.

IMHO there should be a grace period between Java 8 support deprecation and 
the actual removal. Maybe 6 months or so.

BR, Oleg

On Tuesday, April 27, 2021 at 7:13:17 PM UTC+2 slide wrote:

> I agree with dropping java 8. There are some nice features in 11 that 
> would be good to use.
>
> On Tue, Apr 27, 2021 at 9:11 AM Tim Jacomb  wrote:
>
>> We’ve been using it for over a year on java 11 and never hit an issue...
>>
>> I would rather drop java 8 as well
>>
>> On Tue, 27 Apr 2021 at 15:48, Jesse Glick  wrote:
>>
>>> My opinion remains that if we believe Java 11 support is solid enough to 
>>> be the default, then we may as well keep things simple and drop Java 8 
>>> support: start building core and important plugins with `java.level=11`, 
>>> and take advantage of its features. Building and testing primarily against 
>>> 8 while pushing users to run 11, and forcing developers to consider both 
>>> platforms in every situation, seems like the worst decision.
>>>
>>> -- 
>>> 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/CANfRfr2hjuPWgK7XqzwezcT8eP1i1_ZZd_iMNreg%3D7K7FTzH8Q%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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifVe04fx-7vx6Dp-jkLmTvepCDGHXqRDLEWdHyNN8TG%3Dw%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> Website: http://earl-of-code.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/74c9f96d-1acc-4315-9fd5-e59bb6fdeff8n%40googlegroups.com.

Re: AppCenter Plugin up for adoption

[Oleg Nenashev]

Thanks for all your contributions Mez!
I have updated the default in Jira. Should you ever be interested to 
contribute again to Jenkins, you are more than welcome!

P.S: And thanks for your feedback :) 

On Tuesday, April 27, 2021 at 7:45:02 PM UTC+2 mez.p...@gmail.com wrote:

> I've raised a PR to remove permissions for upload 
> . 
> I've also removed myself from the github team for the plugin. But could I 
> also be removed as the default assignee in JIRA please. Cheers.
>
> On Tuesday, 27 April 2021 at 18:09:12 UTC+1 Mez Pahlan wrote:
>
>> Hi everyone
>>
>> Sadly I can no longer continue to maintain the AppCenter Plugin for 
>> Jenkins. :(. In line with the guidance 
>> 
>>  
>> I am announcing this decision here. 
>>
>> If anyone is interested then please apply to take over the maintenance. I 
>> will shortly put the plugin up for adoption.
>>
>> https://github.com/jenkinsci/appcenter-plugin
>>
>> Thank you all for your help and patience with me over the years I have 
>> learned a lot. Especial thanks to Oleg. You've been super brilliant!
>>
>> Mez
>>
>

-- 
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/60ccd8b8-42d9-48fa-bf71-7d6d67fe19f9n%40googlegroups.com.

Re: Jenkins LTS baseline selection

[Tim Jacomb]

2.289 is selected

On Tue, 27 Apr 2021 at 16:25, Beatriz Munoz  wrote:

> Hi!
>
> So, is selected 2.289 or the discussion is still open?
>
> Thanks!
>
> El 24 abr 2021, a las 17:55, Tim Jacomb  escribió:
>
> Agreed
>
> On Sat, 24 Apr 2021 at 14:25, Oleg Nenashev 
> wrote:
>
>> AFAICT there have been no new regressions reported for 2.289 since the
>> release.
>> I think we can go ahead with choosing this baseline.
>>
>> BR, Oleg
>>
>> On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com
>> wrote:
>>
>>> 2.289 looks good for me
>>>
>>> El 20 abr 2021, a las 12:43, Oleg Nenashev 
>>> escribió:
>>>
>>> 2.289 looks good for me. There are no major changes (e.g. we did not
>>> merge the Jetty 9.4.40 update), and it should be safe to take this versions
>>> as a baseline. If something happens, we still have 6 weeks
>>>
>>> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com
>>> wrote:
>>>
 2.289 LGTM

 Best,
 Ildefonso

 On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell 
 wrote:

> Hey Tim,
>
> I'm entirely for 2.289 as 2.289 does not make any major changes and as
> Daniel has pointed out, we can backport any fixes.
>
> Cheers,
> Raihaan
>
> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus 
> wrote:
>
>> Thanks for raising this Tim.
>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>>
>> Can you please confirm the expected timeline, so we can better assess
>> things?
>> Re-reading https://www.jenkins.io/download/lts/ we're looking at a
>> .1 6 weeks from now, i.e. some time around 2021-06-02 right ?
>>
>> If so, I agree even choosing the upcoming 2.289 could be acceptable
>> with such a testing period.
>>
>> -- Baptiste
>>
>>
>>
>>
>> Given the expected usua
>>
>>
>>
>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a
>> écrit :
>>
>>> Hello everyone,
>>>
>>> Please voice your opinion on which version should be our next core
>>> baseline.
>>>
>>> For me it looks like either 2.288 or 2.289 are the options
>>>
>>> 2.289 (being released today) includes a change for an upcoming
>>> firefox version so it would be good to get it in, but it hasn't had any
>>> weekly soaking time so we could use 2.288 and then backport it in if we
>>> don't find any issues?
>>>
>>> What do you think?
>>>
>>> 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 jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%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-de...@googlegroups.com.
>
 To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
> 
> .
>


 --
 Ildefonso Montero Pérez
 Senior Software Engineer
 CloudBees, Inc



 E: imon...@cloudbees.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-de...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>>> 

Re: AppCenter Plugin up for adoption

[Mez Pahlan]

I've raised a PR to remove permissions for upload 
. 
I've also removed myself from the github team for the plugin. But could I 
also be removed as the default assignee in JIRA please. Cheers.

On Tuesday, 27 April 2021 at 18:09:12 UTC+1 Mez Pahlan wrote:

> Hi everyone
>
> Sadly I can no longer continue to maintain the AppCenter Plugin for 
> Jenkins. :(. In line with the guidance 
> 
>  
> I am announcing this decision here. 
>
> If anyone is interested then please apply to take over the maintenance. I 
> will shortly put the plugin up for adoption.
>
> https://github.com/jenkinsci/appcenter-plugin
>
> Thank you all for your help and patience with me over the years I have 
> learned a lot. Especial thanks to Oleg. You've been super brilliant!
>
> Mez
>

-- 
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/af6633b6-a29a-413f-b993-59a601452b5fn%40googlegroups.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

[Slide]

I agree with dropping java 8. There are some nice features in 11 that would
be good to use.

On Tue, Apr 27, 2021 at 9:11 AM Tim Jacomb  wrote:

> We’ve been using it for over a year on java 11 and never hit an issue...
>
> I would rather drop java 8 as well
>
> On Tue, 27 Apr 2021 at 15:48, Jesse Glick  wrote:
>
>> My opinion remains that if we believe Java 11 support is solid enough to
>> be the default, then we may as well keep things simple and drop Java 8
>> support: start building core and important plugins with `java.level=11`,
>> and take advantage of its features. Building and testing primarily against
>> 8 while pushing users to run 11, and forcing developers to consider both
>> platforms in every situation, seems like the worst decision.
>>
>> --
>> 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/CANfRfr2hjuPWgK7XqzwezcT8eP1i1_ZZd_iMNreg%3D7K7FTzH8Q%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/CAH-3BifVe04fx-7vx6Dp-jkLmTvepCDGHXqRDLEWdHyNN8TG%3Dw%40mail.gmail.com
> 
> .
>


-- 
Website: http://earl-of-code.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/CAPiUgVe82RmtyEjbeqKxGc0Cra_1DCxzJZpppjASw4bQxwZoEw%40mail.gmail.com.

AppCenter Plugin up for adoption

[Mez Pahlan]

Hi everyone

Sadly I can no longer continue to maintain the AppCenter Plugin for 
Jenkins. :(. In line with the guidance 

 
I am announcing this decision here. 

If anyone is interested then please apply to take over the maintenance. I 
will shortly put the plugin up for adoption.

https://github.com/jenkinsci/appcenter-plugin

Thank you all for your help and patience with me over the years I have 
learned a lot. Especial thanks to Oleg. You've been super brilliant!

Mez

-- 
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/38b338df-91a4-4f5a-bb9f-ebe9949d8ec3n%40googlegroups.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

[Tim Jacomb]

We’ve been using it for over a year on java 11 and never hit an issue...

I would rather drop java 8 as well

On Tue, 27 Apr 2021 at 15:48, Jesse Glick  wrote:

> My opinion remains that if we believe Java 11 support is solid enough to
> be the default, then we may as well keep things simple and drop Java 8
> support: start building core and important plugins with `java.level=11`,
> and take advantage of its features. Building and testing primarily against
> 8 while pushing users to run 11, and forcing developers to consider both
> platforms in every situation, seems like the worst decision.
>
> --
> 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/CANfRfr2hjuPWgK7XqzwezcT8eP1i1_ZZd_iMNreg%3D7K7FTzH8Q%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/CAH-3BifVe04fx-7vx6Dp-jkLmTvepCDGHXqRDLEWdHyNN8TG%3Dw%40mail.gmail.com.

Re: ScheduledFutures and Cancelling?

[Jesse Glick]

On Tue, Apr 27, 2021 at 11:16 AM Bryan Stopp  wrote:

> who's responsible for calling "cancel()" on the timer?
>

If you started a recurrent timer, then you are responsible for cancelling
it eventually. Nothing to do with Pipeline.

I would normally write this idiom by using plain `schedule` and then inside
the block calling `schedule` again if the goal was *not* realized as
expected, but I suppose it amounts to the same thing.

-- 
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/CANfRfr2%3DjZf3HHd_RxdZdDq3AQcozMutzxv5zrQKUZseiUd93A%40mail.gmail.com.

Re: Jenkins LTS baseline selection

[Beatriz Munoz]

Hi!

So, is selected 2.289 or the discussion is still open?

Thanks!

> El 24 abr 2021, a las 17:55, Tim Jacomb  escribió:
> 
> Agreed
> 
> On Sat, 24 Apr 2021 at 14:25, Oleg Nenashev  > wrote:
> AFAICT there have been no new regressions reported for 2.289 since the 
> release.
> I think we can go ahead with choosing this baseline.
> 
> BR, Oleg
> 
> On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com 
>  wrote:
> 2.289 looks good for me
> 
> 
>> El 20 abr 2021, a las 12:43, Oleg Nenashev > escribió:
>> 
> 
>> 2.289 looks good for me. There are no major changes (e.g. we did not merge 
>> the Jetty 9.4.40 update), and it should be safe to take this versions as a 
>> baseline. If something happens, we still have 6 weeks
>> 
>> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com 
>>  wrote:
>> 2.289 LGTM
>> 
>> Best,
>> Ildefonso
>> 
>> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell > 
>> wrote:
>> Hey Tim,
>> 
>> I'm entirely for 2.289 as 2.289 does not make any major changes and as 
>> Daniel has pointed out, we can backport any fixes.
>> 
>> Cheers,
>> Raihaan
>> 
>> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus > wrote:
>> Thanks for raising this Tim. 
>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>> 
>> Can you please confirm the expected timeline, so we can better assess things?
>> Re-reading https://www.jenkins.io/download/lts/ 
>>  we're looking at a .1 6 weeks from 
>> now, i.e. some time around 2021-06-02 right ?
>> 
>> If so, I agree even choosing the upcoming 2.289 could be acceptable with 
>> such a testing period. 
>> 
>> -- Baptiste
>> 
>> 
>> 
>> 
>> Given the expected usua
>> 
>> 
>> 
>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb > a écrit :
>> Hello everyone,
>> 
>> Please voice your opinion on which version should be our next core baseline.
>> 
>> For me it looks like either 2.288 or 2.289 are the options
>> 
>> 2.289 (being released today) includes a change for an upcoming firefox 
>> version so it would be good to get it in, but it hasn't had any weekly 
>> soaking time so we could use 2.288 and then backport it in if we don't find 
>> any issues?
>> 
>> What do you think?
>> 
>> 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 jenkinsci-de...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%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-de...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%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-de...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
>>  
>> .
>> 
>> 
>> -- 
>> Ildefonso Montero Pérez
>> Senior Software Engineer
>> CloudBees, Inc
>> 
>> 
>> 
>> E: imon...@cloudbees.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-de...@googlegroups.com <>.
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>>  
>> .
> 
> Beatriz Muñoz Manso
> Sr Software 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 fr

Re: LTS 2.277.4 RC

[Jesse Glick]

On Tue, Apr 27, 2021 at 8:52 AM Tim Jacomb  wrote:

> The RC is
> http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT/jenkins-war-2.277.4-20210427.105011-1.war
>

 Would be nice to use incrementals for this purpose but it seems that ATH
is getting in the way?

https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.277/13/testReport/

-- 
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/CANfRfr1yT8-w1_qCWQWMjJhNfCCJh0Je9-BjrTsmg4ipduoQmA%40mail.gmail.com.

Re: ScheduledFutures and Cancelling?

[Bryan Stopp]

Right - My timer never stopped. So my question is: who's responsible for
calling "cancel()" on the timer? I assume I am.. but i'm not sure if this
is really a "good practice". My current implementation is here:

https://github.com/bstopp/adobe-cloud-manager-plugin/blob/860f54a3ed9914939e339b04a1664fd21d85cf49/src/main/java/io/jenkins/plugins/adobe/cloudmanager/step/PollPipelineStep.java#L139-L156

Grateful for any pointers and/or criticism.

Thanks!

-B

On Tue, Apr 27, 2021 at 9:44 AM Jesse Glick  wrote:

> On Mon, Apr 26, 2021 at 11:04 PM Bryan Stopp 
> wrote:
>
>> I'm getting an error:
>>
>> completed: already completed CpsStepContext
>>
>> after my timer has called the onSuccess method
>>
>
> Somehow you are calling `onSuccess` and/or `onFailure` two or more times,
> which is illegal. The warning is not fatal (subsequent calls are ignored)
> but may be indicative of a real bug.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/TpUAft3fSxE/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANfRfr1gK-7kdteh6-uJfWWQbqf%2B2s-tL-9LpwChGEa5fBVZ5w%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/CAGiOsN_za%3DqRk3aFZGsrmPyhZsARnpi0j5tq9z4fUvHQR9ZxVQ%40mail.gmail.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

[Jesse Glick]

My opinion remains that if we believe Java 11 support is solid enough to be
the default, then we may as well keep things simple and drop Java 8
support: start building core and important plugins with `java.level=11`,
and take advantage of its features. Building and testing primarily against
8 while pushing users to run 11, and forcing developers to consider both
platforms in every situation, seems like the worst decision.

-- 
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/CANfRfr2hjuPWgK7XqzwezcT8eP1i1_ZZd_iMNreg%3D7K7FTzH8Q%40mail.gmail.com.

Re: ScheduledFutures and Cancelling?

[Jesse Glick]

On Mon, Apr 26, 2021 at 11:04 PM Bryan Stopp  wrote:

> I'm getting an error:
>
> completed: already completed CpsStepContext
>
> after my timer has called the onSuccess method
>

Somehow you are calling `onSuccess` and/or `onFailure` two or more times,
which is illegal. The warning is not fatal (subsequent calls are ignored)
but may be indicative of a real bug.

-- 
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/CANfRfr1gK-7kdteh6-uJfWWQbqf%2B2s-tL-9LpwChGEa5fBVZ5w%40mail.gmail.com.

Re: LTS 2.277.4 RC

[Tim Jacomb]

The RC is
http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT/jenkins-war-2.277.4-20210427.105011-1.war

(in case anyone else uploads something in the meantime)

Thanks
Tim

On Tue, 27 Apr 2021 at 12:49, Oleg Nenashev  wrote:

> Thanks all!
> Draft changelog and upgrade guidelines are also available for review:
> https://github.com/jenkins-infra/jenkins.io/pull/4280
>
>
> On Tuesday, April 27, 2021 at 12:56:43 PM UTC+2 bmu...@cloudbees.com
> wrote:
>
>> Hi all!!
>>
>> Release candidate is ready to be tested:
>> http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT
>>
>> Thanks Daniel Beck, Mark Waite and Tim Jacomb for the support!
>>
>>
>> El 21 abr 2021, a las 12:08, Beatriz Munoz 
>> escribió:
>>
>> PR for backports: https://github.com/jenkinsci/jenkins/pull/5441
>>
>> El 21 abr 2021, a las 11:47, Beatriz Munoz 
>> escribió:
>>
>> I volunteer for .4 release lead but I would need someone else guidance
>>
>>
>> El 21 abr 2021, a las 11:41, timja...@gmail.com 
>> escribió:
>>
>> Hello
>>
>> If you have time please create a PR for the backports
>>
>> > PD: Something else, I saw that we are not publishing release candidate
>> wars into http://mirrors.jenkins-ci.org/war-stable-rc/, Does the process
>> change and we are not publishing anymore?
>>
>> No, there didn't seem to be any point, I've been uploading them to
>> artifactory as part of publishing it.
>>
>> Thanks
>> Tim
>>
>> On Wednesday, 21 April 2021 at 10:37:20 UTC+1 Oleg Nenashev wrote:
>>
>>> Hi Beatriz,
>>>
>>> With the recent .3 security release, the entire Release team was quite
>>> busy with the out-of-band work.
>>> AFAICT we do not even have a release lead identified for .4 yet. We need
>>> volunteers, right?
>>>
>>> P.S: I would be happy to volunteer, but I am snowed under other work
>>> threads. If I have spare time, I will help with Hosting request handling
>>> which needs a makeshift solution
>>>
>>> BR, Oleg
>>>
>>> On Wednesday, April 21, 2021 at 10:14:23 AM UTC+2 bmu...@cloudbees.com
>>> wrote:
>>>
 Hi devs!

 Next LTS will be on 5th May, Today is the day for RC, but I cannot see
 it any PR in the repository with the backports. I’ve just checked
 https://issues.jenkins.io/browse/JENKINS-65021?filter=12146 and there
 are 6 tickets there:

 - https://issues.jenkins.io/browse/JENKINS-65021
 - https://issues.jenkins.io/browse/JENKINS-65327
 - https://issues.jenkins.io/browse/JENKINS-65308
 - https://issues.jenkins.io/browse/JENKINS-65336
 - https://issues.jenkins.io/browse/JENKINS-56934
 - https://issues.jenkins.io/browse/JENKINS-65281

 There is something else that needs to be included? Please just let me
 know.  I will create the PR for the backports.

 PD: Something else, I saw that we are not publishing release candidate
 wars into http://mirrors.jenkins-ci.org/war-stable-rc/, Does the
 process change and we are not publishing anymore?

 Thanks


 Beatriz Muñoz Manso
 Sr Software 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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/703f7ea2-455d-4333-83d8-5a7fdf042d56n%40googlegroups.com
>> 
>> .
>>
>>
>> Beatriz Muñoz Manso
>> Sr Software Engineer
>> CloudBees, Inc.
>>
>> 
>>
>>
>> Beatriz Muñoz Manso
>> Sr Software Engineer
>> CloudBees, Inc.
>>
>> 
>>
>>
>> Beatriz Muñoz Manso
>> Sr Software 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/71784bfe-8b5a-4a59-bb7d-22b85fb5bc63n%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-3Bic2967PwgxfFdQU_HLkGyYWtF59BewUiRtthyb4QnwJxQ%40mail.gmail.com.

Re: LTS 2.277.4 RC

[Oleg Nenashev]

Thanks all!
Draft changelog and upgrade guidelines are also available for 
review: https://github.com/jenkins-infra/jenkins.io/pull/4280


On Tuesday, April 27, 2021 at 12:56:43 PM UTC+2 bmu...@cloudbees.com wrote:

> Hi all!!
>
> Release candidate is ready to be tested: 
> http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT
>
> Thanks Daniel Beck, Mark Waite and Tim Jacomb for the support!
>
>
> El 21 abr 2021, a las 12:08, Beatriz Munoz  
> escribió:
>
> PR for backports: https://github.com/jenkinsci/jenkins/pull/5441
>
> El 21 abr 2021, a las 11:47, Beatriz Munoz  
> escribió:
>
> I volunteer for .4 release lead but I would need someone else guidance
>
>
> El 21 abr 2021, a las 11:41, timja...@gmail.com  
> escribió:
>
> Hello 
>
> If you have time please create a PR for the backports
>
> > PD: Something else, I saw that we are not publishing release candidate 
> wars into http://mirrors.jenkins-ci.org/war-stable-rc/, Does the process 
> change and we are not publishing anymore?
>
> No, there didn't seem to be any point, I've been uploading them to 
> artifactory as part of publishing it.
>
> Thanks
> Tim
>
> On Wednesday, 21 April 2021 at 10:37:20 UTC+1 Oleg Nenashev wrote:
>
>> Hi Beatriz,
>>
>> With the recent .3 security release, the entire Release team was quite 
>> busy with the out-of-band work.
>> AFAICT we do not even have a release lead identified for .4 yet. We need 
>> volunteers, right?
>>
>> P.S: I would be happy to volunteer, but I am snowed under other work 
>> threads. If I have spare time, I will help with Hosting request handling 
>> which needs a makeshift solution
>>
>> BR, Oleg
>>
>> On Wednesday, April 21, 2021 at 10:14:23 AM UTC+2 bmu...@cloudbees.com
>> wrote:
>>
>>> Hi devs!
>>>
>>> Next LTS will be on 5th May, Today is the day for RC, but I cannot see 
>>> it any PR in the repository with the backports. I’ve just checked 
>>> https://issues.jenkins.io/browse/JENKINS-65021?filter=12146 and there 
>>> are 6 tickets there:
>>>
>>> - https://issues.jenkins.io/browse/JENKINS-65021
>>> - https://issues.jenkins.io/browse/JENKINS-65327
>>> - https://issues.jenkins.io/browse/JENKINS-65308
>>> - https://issues.jenkins.io/browse/JENKINS-65336
>>> - https://issues.jenkins.io/browse/JENKINS-56934
>>> - https://issues.jenkins.io/browse/JENKINS-65281
>>>
>>> There is something else that needs to be included? Please just let me 
>>> know.  I will create the PR for the backports.
>>>
>>> PD: Something else, I saw that we are not publishing release candidate 
>>> wars into http://mirrors.jenkins-ci.org/war-stable-rc/, Does the 
>>> process change and we are not publishing anymore?
>>>
>>> Thanks
>>>
>>>
>>> Beatriz Muñoz Manso
>>> Sr Software 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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/703f7ea2-455d-4333-83d8-5a7fdf042d56n%40googlegroups.com
>  
> 
> .
>
>
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
>
>  
>
>
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
>
>  
>
>
> Beatriz Muñoz Manso
> Sr Software 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/71784bfe-8b5a-4a59-bb7d-22b85fb5bc63n%40googlegroups.com.

Re: Proposal: Making the Hosting team official (and onboarding new members)

[Oleg Nenashev]

Hi all,

Thanks to everyone who contributed to Hosting request processing as a part 
of the previous discussions. As you may have seen in another thread, Alex 
has stepped down from leading the Hosting team. Thanks a lot to Alex for 
all the contributions and the hosting process automation! We will be 
looking for a new team lead and more contributors, anyone is welcome!

I have started a Doodle for the knowledge transfer session about the 
Hosting 
process: 
https://doodle.com/poll/xiqmx4hxfdt8s4in?utm_source=poll&utm_medium=link 
. Hopefully Alex would be available so that we could discuss and document 
parts not yet documented in https://www.jenkins.io/project/teams/hosting/ 
and other related pages. If you are interested to contribute, please vote 
for the timeslots!

Best regards,
Oleg Nenashev
Jenkins Board Member

On Tuesday, May 19, 2020 at 12:04:15 AM UTC+2 slide wrote:

> FYI, there are a couple of hosting requests that could use a review right 
> now if anyone wants to take a look. I am going to put up a page on 
> jenkins.io for things to look for in the code. I would recommend waiting 
> until the automated checker (it shows up as me, Alex Earl) marks things as 
> good to go for a human review of the code. Before that happens, the 
> developers of the plugin need to have certain things in place and correct 
> before we even consider doing a review of the code. I'll try and get that 
> doc up on jenkins.io this week.
>
>
> On Friday, May 15, 2020 at 6:51:33 AM UTC-7, YanJun Shi wrote:
>
>> Okay. Thank you for your help, Oleg. I already have done the 4 steps, Is 
>> there any other steps I need to do？
>>
>>
>>1. 
>>
>>Subscribe to the Jenkins Developer Mailing list 
>>
>>2. 
>>
>>Subscribe to the HOSTING project 
>> in Jenkins Jira
>>3. 
>>
>>Subscribe to the Repository Permission Updater 
>>
>> repository
>>4. 
>>
>>Subscribe to the Jenkins Update Center 
>> repository
>>
>>
>> On Fri, May 15, 2020 at 3:58 AM Oleg Nenashev  
>> wrote:
>>
> Hi, thanks for your interest! You are welcome to join and to start 
>>> contributing to hosting reviews. No special permissions needed to get 
>>> started: 
>>> https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews
>>>
>>> And thanks for submitting ICLA!
>>>
>>> On Sun, May 10, 2020, 04:45 YanJun Shi  wrote:
>>>
>> I hope to join this team and contribute my strength

 On Wednesday, April 29, 2020 at 5:09:27 PM UTC+8, Oleg Nenashev wrote:
>
> Hi all,
>
>
> In the Jenkins community we have an unofficial Hosting team which 
> handles various requests related to plugin hosting (forking/transferring 
> plugins, managing permissions and update center blacklists, etc.) There 
> are 
> multiple contributors involved in this activity on a regular basis, and 
> it 
> would be great to document these processes so that we could use these 
> docs 
> as a reference and as guidelines for onboarding new contributors to help 
> with the hosting process. I would propose to create an official team and 
> to 
> introduce an onboarding process:
>
> Proposal
>
>- Make the "Hosting Team" official, document its roles somewhere 
>on jenkins.io. Scope: plugin and component hosting on Jenkins 
>resources (GitHub, Update Centers, etc.)
>- Grant permissions to active contributors who are interested and 
>who already have experience with the hosting process (e.g. Tim Jacomb, 
>Wadeck Follonier)
>- Create new HOSTING/Mailing list triage guidelines
>- Invite interested contributors to help with triage of hosting 
>requests as a first onboarding step to get permissions needed for 
> GitHub / 
>Update Site and Repository Permission Updater management
>
> Team Responsibilities. Below there are some current responsibilities 
> related to the hosting process. This list is likely incomplete, please 
> feel 
> free to add more items.
>
>- Triage and processing of new plugin HOSTING requests in Jenkins 
>Jira. Currently Alex Earl champions it, and there are only a few 
>contributors who help with the requests triage. Such triage is 
> instrumental 
>to...
>   - Ensuring hosted plugins have proper artifactIds. We cannot 
>   easily change them later...
>   - Do sanity check of plugins for security issues. Thanks to 
>   Alex Earl and the security team for handling it
>   - Checking for duplication with existing plugins 
>   
> 

Re: Plugin Hosting Requests

[Oleg Nenashev]

Hi all,

I have started a Doodle for the knowledge transfer session about the Hoting 
process: 
https://doodle.com/poll/xiqmx4hxfdt8s4in?utm_source=poll&utm_medium=link 
. Hopefully Alex would be available so that we could discuss and document 
parts not yet documented in https://www.jenkins.io/project/teams/hosting/ 
and other related pages. If you are interested to contribute, please vote 
for the timeslots!

Best regards,
Oleg

On Tuesday, April 13, 2021 at 8:16:39 PM UTC+2 Oleg Nenashev wrote:

> Hi all,
>
> Is anyone interested in mentorship from the Jenkins contributors to become 
> a part of the hosting team?
> I am organizing the onboarding process for event organizers, and I can 
> help with the Hosting team as well.
>
> Best regards,
> Oleg
>
>
> On Tuesday, April 6, 2021 at 1:47:14 PM UTC+2 Olblak wrote:
>
>> Hi,
>>
>> Thank you Alex for your email, I am really glad when we have the time to 
>> correctly prepare that kind of transition.
>> I mean It's totally normal that contribution time evolves.  :) 
>> This sounds like the perfect time for someone to step up, and I would be 
>> very happy to help with that transition.
>>
>>
>> On Fri, Apr 2, 2021, at 4:33 PM, Oleg Nenashev wrote:
>>
>> Thanks a lot for all your contributions Alex!
>>
>> Last year we have started the Hosting Team 
>>  in Jenkins, but 
>> unfortunately it did not fly. At least we have several contributors with 
>> permissions and up-to-date guidelines for the hosting process. There was 
>> also a significant improvement in the hosting process automation, thanks to 
>> Alex and Tim.
>>
>> I used to maintain the hosting process several years ago, and I will be 
>> able to help with processing hosting requests. My time is also limited, and 
>> it would be great to have more contributors involved. I will be happy to 
>> provide mentorship to those who are interested.
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>>
>> On Friday, April 2, 2021 at 3:55:05 PM UTC+2 adityasriva...@gmail.com 
>> wrote:
>>
>>
>> On Fri, Apr 2, 2021 at 4:58 PM Mark Waite  wrote:
>>
>> That's great Aditya.  We're glad to have additional help.  I'm not the 
>> hosting expert, but wanted to thank you for joining the infrastructure 
>> meeting last week.  We look forward to involving in the Jenkins project in 
>> more ways.  Thanks again!
>>
>>
>> Hello Mark, 
>> The pleasure was all mine. I was truly amazed by looking at the numbers 
>> of daily downloads and TBs level data that moves around. Also had a chat 
>> later with Gareth about the same on an ad-hoc call. Learning a lot :)
>>
>> Thanks and regards,
>> Aditya Srivastava
>>
>>  
>>
>>
>> On Friday, April 2, 2021 at 5:18:02 AM UTC-6 adityasriva...@gmail.com 
>> wrote:
>>
>>
>> Hey Alex,
>> I am a newbie here, so I am not sure if I am eligible, but I sure 
>> am interested in helping out. 
>> I'd love to learn more about the screening part and I've done code 
>> reviews before for my _small_ open-source org, so I guess that experience 
>> would come in handy. 
>> I am excited to learn more about this and get involved. 
>>
>> Thanks and Regards,
>> Aditya Srivastava
>>
>>
>>
>> On Fri, Apr 2, 2021 at 10:22 AM 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>> I'm not sure its a good idea for me to take on more tasks, but I can help 
>> out more if needed. That being said, the dev list is full of people 
>> contributing, it might be worth asking on the users mailing list to see if 
>> there's anyone new interested in helping out, at least the first round of 
>> screening new hosting requests.
>>
>> On Thu, Apr 1, 2021 at 8:06 PM Slide  wrote:
>>
>> Hi Everyone,
>>
>> As I brought up last year, I am having less time to work on Jenkins 
>> because of work responsibilities. It's time for me to reduce my time on 
>> Jenkins again sadly. I have been handling many of the plugin hosting 
>> requests that come in, running the checker and doing code reviews on the 
>> plugins prior to them being accepted into the jenkinsci org on GitHub. I 
>> will no longer have time to do that in the near future and would like to 
>> help migrate that work to someone else who is interested in helping out the 
>> project. Is anyone interested in learning about this and becoming involved?
>>
>> Regards,
>>
>> Alex
>>
>>
>>
>> -- 
>> Website: http://earl-of-code.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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfAFnGYSLe3gUC-qGzPYwEHBfKYTRnd%3DUUYH%2BtpGF8pMQ%40mail.gmail.com
>>  
>> 
>> .
>>
>>
>> -- 
>> Y

Re: LTS 2.277.4 RC

[Beatriz Munoz]

Hi all!!

Release candidate is ready to be tested: 
http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.277.4-SNAPSHOT
 


Thanks Daniel Beck, Mark Waite and Tim Jacomb for the support!

> El 21 abr 2021, a las 12:08, Beatriz Munoz  escribió:
> 
> PR for backports: https://github.com/jenkinsci/jenkins/pull/5441 
> 
> 
>> El 21 abr 2021, a las 11:47, Beatriz Munoz > > escribió:
>> 
>> I volunteer for .4 release lead but I would need someone else guidance
>> 
>> 
>>> El 21 abr 2021, a las 11:41, timja...@gmail.com  
>>> mailto:timjaco...@gmail.com>> escribió:
>>> 
>>> Hello 
>>> 
>>> If you have time please create a PR for the backports
>>> 
>>> > PD: Something else, I saw that we are not publishing release candidate 
>>> > wars into http://mirrors.jenkins-ci.org/war-stable-rc/ 
>>> > , Does the process change 
>>> > and we are not publishing anymore?
>>> 
>>> No, there didn't seem to be any point, I've been uploading them to 
>>> artifactory as part of publishing it.
>>> 
>>> Thanks
>>> Tim
>>> 
>>> On Wednesday, 21 April 2021 at 10:37:20 UTC+1 Oleg Nenashev wrote:
>>> Hi Beatriz,
>>> 
>>> With the recent .3 security release, the entire Release team was quite busy 
>>> with the out-of-band work.
>>> AFAICT we do not even have a release lead identified for .4 yet. We need 
>>> volunteers, right?
>>> 
>>> P.S: I would be happy to volunteer, but I am snowed under other work 
>>> threads. If I have spare time, I will help with Hosting request handling 
>>> which needs a makeshift solution
>>> 
>>> BR, Oleg
>>> 
>>> On Wednesday, April 21, 2021 at 10:14:23 AM UTC+2 bmu...@cloudbees.com 
>>> wrote:
>>> Hi devs!
>>> 
>>> Next LTS will be on 5th May, Today is the day for RC, but I cannot see it 
>>> any PR in the repository with the backports. I’ve just checked 
>>> https://issues.jenkins.io/browse/JENKINS-65021?filter=12146 
>>>  and there are 
>>> 6 tickets there:
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-65021 
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-65327 
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-65308 
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-65336 
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-56934 
>>> 
>>> - https://issues.jenkins.io/browse/JENKINS-65281 
>>> 
>>> 
>>> There is something else that needs to be included? Please just let me know. 
>>>  I will create the PR for the backports.
>>> 
>>> PD: Something else, I saw that we are not publishing release candidate wars 
>>> into http://mirrors.jenkins-ci.org/war-stable-rc/ 
>>> , Does the process change and 
>>> we are not publishing anymore?
>>> 
>>> Thanks
>>> 
>>> 
>>> Beatriz Muñoz Manso
>>> Sr Software 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/703f7ea2-455d-4333-83d8-5a7fdf042d56n%40googlegroups.com
>>>  
>>> .
>> 
>> Beatriz Muñoz Manso
>> Sr Software Engineer 
>> CloudBees, Inc.
>> 
>> 
>> 
> 
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
> 
> 
> 

Beatriz Muñoz Manso
Sr Software 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/D2244979-CEA2-4950-8D21-85ED915F1019%40cloudbees.com.

Re: Deprecating ruby-runtime

[Oleg Nenashev]

JEP update is ready for review: https://github.com/jenkinsci/jep/pull/356 .
There are some changes in the rollout plan we discussed with Daniel Beck on
Monday, some reviews and alignment might be required



On Wed, Apr 21, 2021 at 9:00 AM Oleg Nenashev 
wrote:

> I added the topic to the Governance meeting agenda just in case more
> discussion is needed.
> https://github.com/jenkins-infra/jenkins.io/pull/4256 is almost ready to
> go IMHO, but, as Daniel Beck commented, we also need to do something about
> JEP-7: https://github.com/jenkinsci/jep/tree/master/jep/7 . I will try
> contributing to that if my time allows
>
> BR, Oleg
>
>
> On Friday, April 16, 2021 at 7:18:52 PM UTC+2 Oleg Nenashev wrote:
>
>> It might work on Java 11, bit I see no much reason in even trying. If we
>> drop the Ruby ecosystem, Python should go as well IMHO
>>
>> On Fri, Apr 16, 2021, 18:49 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> There's only a single python plugin, so I think we should include python
>>> in this announcement too
>>>
>>> https://plugins.jenkins.io/python-wrapper/#dependencies
>>>
>>> the install shield plugin only has 200 installs and I suspect it also
>>> won't work right in java 11?
>>>
>>> Gavin
>>>
>>> On Fri, Apr 16, 2021 at 7:00 AM Jesse Glick 
>>> wrote:
>>>
 On Fri, Apr 16, 2021 at 6:09 AM Oleg Nenashev 
 wrote:

> [Regarding] removing the JEP-200 Ruby Runtime exceptions and XStream
> converters from the Jenkins core […] we should set a grace period, e.g.
> announce this change with a 6-month advance so that users have an
> opportunity to migrate to other plugins.
>

 I do not see any need to wait that long. Just do it and announce it
 applies to the next weekly. The next LTS upgrade guide will mention this of
 course. Users have the “opportunity” to migrate to other plugins whenever
 they want, or simply decline to update Jenkins core.

 --
 You received this message because you are subscribed to a topic in the
 Google Groups "Jenkins Developers" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3sVd6Qkgwq4M930_OJi%2BNVvyCjL5ubiQTGAPhK_KK3QA%40mail.gmail.com
 
 .

>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut%3Dg85m6LXLEF2rs71CvHtDjJt-nfvPdHtwtWwtyAK52g%40mail.gmail.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> To unsubscribe from this group and all its topics, 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/e0ca17aa-9bb1-4c9a-8a3c-c1c48f6806d6n%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/CAPfivLA2u4LXzJci8VJBsxMpvajPJVVnxj15imqNFAqG6tfaEA%40mail.gmail.com.

Re: Plugin end-of-life (EOL) policy

[Baptiste Mathus]

Oh, and: given the nature of our project, I think defining a clear way to
un-EOL a plugin would likely be needed too.
It's probable that we'll EOL some plugins, and after say 1 or 2 years some
folks will want to revive some of the plugins that got EOLed.

It may seem backward, but I think it's a healthy thing. The bottom line and
expectation is that anyway we'll probably EOL dozens of plugins quickly and
only a handful will be requested to be unEOLed (meaning, after a
transitional pre-EOL warning period and nobody has complained during this
one).

-- Baptiste

Le mar. 27 avr. 2021 à 09:24, Baptiste Mathus  a écrit :

> I agree this is an initiative definitely worth pursuing. We all know this
> is a pain.
>
> On criteria for defining whether a plugin should be EOLed, I think the
> best idea I have seen so far was Stephen's:
>
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-dev/Ih0RviQ0G90/NmoVJQ1j6NAJ
>
> Basically automated regular PRs allowing for a global detection of plugins
> without an active maintainer.
> That maintainer's existence/reactivity + some criteria TBD (like last
> release date, the number of open jira issues, etc.) would help us decide
> whether or not start an EOL process.
>
> Anyway, however we define these criteria, which discussion I think we can
> handle separately, defining an EOL process I think has become vital indeed
> for the Jenkins Project to keep thriving.
>
>
> Le mar. 27 avr. 2021 à 04:00, Basil Crow  a écrit :
>
>> Abandoned plugins cause friction for both Jenkins users and contributors
>> alike.
>>
>> They cause friction for users because they are unlikely to be simpatico
>> with newer features like Pipeline. In the worst case, they are downright
>> incompatible with newer features like Configuration Form Modernization
>> and cause breakage that is difficult for users to resolve.
>>
>> They cause friction for contributors by making it difficult to perform
>> project-wide changes, such as Configuration Form Modernization or
>> dependency updates.
>>
>> True, distributing as many plugins as possible for as long as possible
>> maximizes the value the project provides and maintains the project's
>> strong reputation for flexibility. Yet, treating abandoned plugins as
>> first-class citizens indefinitely carries a non-trivial cost, and that
>> cost only increases the longer a plugin remains abandoned.
>>
>> The project is over 15 years old, and some plugins have been abandoned
>> for the better part of a decade. Many of these plugins will likely
>> remain abandoned for the next decade. At what point does the cost of
>> carrying these plugins outweigh the benefit?
>>
>> I do not know the answer, but I do know that the answer is not "never".
>> Contributor bandwidth is a finite resource. However, there remain
>> hundreds of plugins that have been abandoned for the better part of a
>> decade yet are seemingly presented as first-class citizens without so
>> much as a deprecation notice. This does not seem sustainable.
>>
>> I would like to propose that we define a process for plugin end-of-life:
>> initially marking such plugins as deprecated, then eventually removing
>> such plugins from distribution.
>>
>> How would we decide when to deprecate a plugin or remove it from
>> distribution? We could use metrics such as the number of days since the
>> last release and the number of installations. For example, we could
>> declare that any plugin that has not been released in five years would
>> be automatically deprecated and that any plugin that has remained
>> deprecated for more than five years would be removed from distribution.
>> We could put escape hatches in place to exempt sufficiently popular
>> plugins from this policy.
>>
>> I do not have a strong preference as to how long the support window
>> should be. But I do have a strong preference that it be finite:
>> supporting an unbounded number of plugins as first-class citizens for an
>> unbounded amount of time does not seem sustainable.
>>
>> I can already hear Oleg calling for a blog post to be written announcing
>> such a policy months in advance of its implementation, were such a
>> policy to be agreed upon. That would be fine by me as well. Again, the
>> point is not to be overly aggressive or to surprise users, but rather to
>> put reasonable limits in place that support the project's long-term
>> goals given the finite resources that are available.
>>
>> --
>> 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/CAFwNDjoNMRbkDdkcjYMZSauCfE%2BRQ6pkv_jGG5W2RTqaDiJM2w%40mail.gmail.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubs

Re: Plugin end-of-life (EOL) policy

[Baptiste Mathus]

I agree this is an initiative definitely worth pursuing. We all know this
is a pain.

On criteria for defining whether a plugin should be EOLed, I think the best
idea I have seen so far was Stephen's:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-dev/Ih0RviQ0G90/NmoVJQ1j6NAJ

Basically automated regular PRs allowing for a global detection of plugins
without an active maintainer.
That maintainer's existence/reactivity + some criteria TBD (like last
release date, the number of open jira issues, etc.) would help us decide
whether or not start an EOL process.

Anyway, however we define these criteria, which discussion I think we can
handle separately, defining an EOL process I think has become vital indeed
for the Jenkins Project to keep thriving.


Le mar. 27 avr. 2021 à 04:00, Basil Crow  a écrit :

> Abandoned plugins cause friction for both Jenkins users and contributors
> alike.
>
> They cause friction for users because they are unlikely to be simpatico
> with newer features like Pipeline. In the worst case, they are downright
> incompatible with newer features like Configuration Form Modernization
> and cause breakage that is difficult for users to resolve.
>
> They cause friction for contributors by making it difficult to perform
> project-wide changes, such as Configuration Form Modernization or
> dependency updates.
>
> True, distributing as many plugins as possible for as long as possible
> maximizes the value the project provides and maintains the project's
> strong reputation for flexibility. Yet, treating abandoned plugins as
> first-class citizens indefinitely carries a non-trivial cost, and that
> cost only increases the longer a plugin remains abandoned.
>
> The project is over 15 years old, and some plugins have been abandoned
> for the better part of a decade. Many of these plugins will likely
> remain abandoned for the next decade. At what point does the cost of
> carrying these plugins outweigh the benefit?
>
> I do not know the answer, but I do know that the answer is not "never".
> Contributor bandwidth is a finite resource. However, there remain
> hundreds of plugins that have been abandoned for the better part of a
> decade yet are seemingly presented as first-class citizens without so
> much as a deprecation notice. This does not seem sustainable.
>
> I would like to propose that we define a process for plugin end-of-life:
> initially marking such plugins as deprecated, then eventually removing
> such plugins from distribution.
>
> How would we decide when to deprecate a plugin or remove it from
> distribution? We could use metrics such as the number of days since the
> last release and the number of installations. For example, we could
> declare that any plugin that has not been released in five years would
> be automatically deprecated and that any plugin that has remained
> deprecated for more than five years would be removed from distribution.
> We could put escape hatches in place to exempt sufficiently popular
> plugins from this policy.
>
> I do not have a strong preference as to how long the support window
> should be. But I do have a strong preference that it be finite:
> supporting an unbounded number of plugins as first-class citizens for an
> unbounded amount of time does not seem sustainable.
>
> I can already hear Oleg calling for a blog post to be written announcing
> such a policy months in advance of its implementation, were such a
> policy to be agreed upon. That would be fine by me as well. Again, the
> point is not to be overly aggressive or to surprise users, but rather to
> put reasonable limits in place that support the project's long-term
> goals given the finite resources that are available.
>
> --
> 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/CAFwNDjoNMRbkDdkcjYMZSauCfE%2BRQ6pkv_jGG5W2RTqaDiJM2w%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/CANWgJS4Y7tdk345Du3ooV87ayxEcgy6yQX2EctyAJ-zv1hwzEw%40mail.gmail.com.