Re: Deprecating ruby-runtime

[Oleg Nenashev]

Hi Gavin,

Did you have a chance to review https://github.com/jenkinsci/jep/pull/356 ?
I think the change is stuck, and it would be great to get it over the line

Best regards,
Oleg


On Tuesday, April 27, 2021 at 11:10:43 AM UTC+2 Oleg Nenashev wrote:

> 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-de...@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/ce60357a-4565-4b00-b159-56ebd5cfbf22n%40googlegroups.com.

Re: Saturday May 29th - Hack, commit, push event

[Oleg Nenashev]

Hi all,

I will likely be available on May 29 since it is Saturday. I will no 
bandwidth to organize the event, but I am ready to help with whatever 
technical advisory side. Mon français est tres mal, mais je vais essayer :) 
I also brought up potential topics in this Twitter thread 
, based on 
the contributors we have in Paris.

At the moment, I suggest 3 topics:

   - Open Telemetry integrations and metrics exposure in plugins. Cyrille 
   and the Elastic team might participate, and I believe Arnaud's advisor 
   plugin could benefit from new metrics as well ()
   - Terminology cleanup, especially for French localizations
   - French localization?

Please add your ideas here. Since it is an online event, any French 
speaking contributors in EMEA-compatible timezones should be able to 
participate.

Best regards,
Oleg Nenashev


On Saturday, May 8, 2021 at 9:52:16 AM UTC+2 Arnaud Héritier wrote:

> Hi team,
>
> At the end of the month their is a one day hackergarten as the event hack 
> commit push. 
>
> There are already various projects as you can see on the website and maybe 
> some of you would like to mentor some jenkins developments ?
>
> https://paris2021.hack-commit-pu.sh/
>
> The event being remote the French nature of the event is less 
> important(speaking French is preferred but not mandatory), it is just the 
> time zone which is (western Europe). 
>
> Feel free to contact the organization team if you are interested or to 
> contact me (I am in contact with them)
>
> Cheers
>
> -- 
> Arnaud Héritier
> Twitter/Skype : aheritier
>

-- 
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/d27c9d6e-f54f-4dc4-a52c-3235983e8fb5n%40googlegroups.com.

Backporting has started and the RC is scheduled for 19th May

[raihaan...@gmail.com]

Candidates: https://issues.jenkins-ci.org/issues/?filter=12146

Fixed: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.289.1-fixed

Rejected: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.289.1-rejected

Cheers,
Raihaan

-- 
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/7e1874d7-7435-4516-ab73-bb80648677b9n%40googlegroups.com.

Re: bom 807 fails dependency checks in git client plugin

[Mark Waite]

On Saturday, May 8, 2021 at 6:10:21 AM UTC-6 Basil Crow wrote:

> I already faced the same issue in jenkinsci/email-ext-plugin#291 
>  and worked 
> around it by adding Caffeine to my  section. Of 
> course the permanent solution is to adapt Script Security to 
> jenkinsci/bom#505 , for which 
> I already opened jenkinsci/script-security-plugin#345 
> .
>

Thanks very much.  That worked great.

Mark Waite 

-- 
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/813f3f4d-2756-42b4-a6ba-f32191f0bff3n%40googlegroups.com.

Re: bom 807 fails dependency checks in git client plugin

[Basil Crow]

I already faced the same issue in jenkinsci/email-ext-plugin#291
 and worked around
it by adding Caffeine to my  section. Of course the
permanent solution is to adapt Script Security to jenkinsci/bom#505
, for which I already opened
jenkinsci/script-security-plugin#345
.

On Sat, May 8, 2021 at 12:12 AM Mark Waite 
wrote:
>
> I tried to update the git client plugin to use bom 807.  The update fails
to compile with a message about the required bounds check failing on the
caffeine library.
>
> Any suggestions of changes I should make in the git client plugin to use
the most recent bill of materials?
>
> https://github.com/jenkinsci/git-client-plugin/pull/702 is the pull
request
>
> Mark Waite
>
> --
> 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/64f55a31-4dfa-4ba9-b15e-aca6e7620864n%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/CAFwNDjq4XvdPrDZV%3D6sAeGtj5Q0%3DVEvxZKtWqnW2DE2yD%3Doegg%40mail.gmail.com.

Re: Looking for release lead for 2.289.1

[Tim Jacomb]

Raihaan time zone shouldn’t  be a problem.

If you’re up for it then please create an issue here:
https://github.com/jenkins-infra/release/issues/new/choose

Carlos please have a look and see if you want to help out, and join us in
#jenkins-release on IRC

Thanks
Tim

On Sat, 8 May 2021 at 04:56, raihaan...@gmail.com 
wrote:

> Hey Tim,
>
> Sure I think I'll be able to find the time to do it.
> As long as my timezone(GMT+8) is not a blocker for anything.
>
> Cheers,
> Raihaan
>
> On Saturday, 8 May 2021 at 06:04:42 UTC+8 Oleg Nenashev wrote:
>
>> If there are no other volunteers, I will find time to coordinate the
>> release if it is not a security one.
>> But it would be really great if somebody else steps up. Maybe James Nord,
>> Raihaan, Basil or Ramon would be interested.
>>
>>
>> On Friday, May 7, 2021 at 10:32:49 AM UTC+2 timja...@gmail.com wrote:
>>
>>> Hello
>>>
>>> Is anyone interested in being the release lead for 2.289.1?
>>>
>>> Planned dates can be seen on the event calendar:
>>> https://www.jenkins.io/events/#event-calendar
>>> Release candidate by 19th May
>>> Release on 2nd June
>>>
>>> The documentation is at:
>>>
>>> https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>>>
>>> I've initialised the release branches already so you won't need direct
>>> merge access anywhere, you will be able to do any pull requests from forks
>>>
>>> I'll be available to answer any questions and provide guidance (along
>>> with hopefully other past release leads)
>>>
>>> We chat in #jenkins-release on freenode IRC,
>>> https://www.jenkins.io/chat/#jenkins-release
>>>
>>> Anyone interested?
>>>
>>> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/40ab2cad-6fbc-41a0-8f79-c836f3f4ecf9n%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-3Biet2SSdebj9VhN_GQtV2x%3DcbCteAq8mmbNkAXLRA0BeHA%40mail.gmail.com.

Saturday May 29th - Hack, commit, push event

[Arnaud Héritier]

Hi team,

At the end of the month their is a one day hackergarten as the event hack
commit push.

There are already various projects as you can see on the website and maybe
some of you would like to mentor some jenkins developments ?

https://paris2021.hack-commit-pu.sh/

The event being remote the French nature of the event is less
important(speaking French is preferred but not mandatory), it is just the
time zone which is (western Europe).

Feel free to contact the organization team if you are interested or to
contact me (I am in contact with them)

Cheers

-- 
Arnaud Héritier
Twitter/Skype : aheritier

-- 
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/CAFNCU-94gAypoP5dqVeK79dd7gVod27iauZ3C5Gs4F1ggLyAhw%40mail.gmail.com.

Re: Looking for release lead for 2.289.1

[Carlos Tadeu Panato Jr]

Thanks for the reply Oleg.
I will read the link.



On Sat 8. May 2021 at 07:51 Oleg Nenashev  wrote:

> Hi Carlos,
>
> This is a really good question. We do not have a "Release shadow" at the
> moment, but sure we could try it. Currently the "release lead" is also a
> rotating contributor who receives advice and mentorship from other release
> team members and the Jenkins Release Officer (Tim Jacomb). So the release
> lead in Jenkins is closer to the Release shadow in K8s.
>
> More info about the Jenkina release team and processes:
> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc
>
> Best regards,
> Oleg
>
>
> On Sat, May 8, 2021, 07:15 Carlos Tadeu Panato Jr 
> wrote:
>
>> Hello Oleg
>>
>> There is a way to be a release shadow and learn all the process before be
>> a release lead?
>>
>> Thanks
>> Carlos
>>
>> On Sat 8. May 2021 at 00:04 Oleg Nenashev  wrote:
>>
>>> If there are no other volunteers, I will find time to coordinate the
>>> release if it is not a security one.
>>> But it would be really great if somebody else steps up. Maybe James
>>> Nord, Raihaan, Basil or Ramon would be interested.
>>>
>>>
>>> On Friday, May 7, 2021 at 10:32:49 AM UTC+2 timja...@gmail.com wrote:
>>>
 Hello

 Is anyone interested in being the release lead for 2.289.1?

 Planned dates can be seen on the event calendar:
 https://www.jenkins.io/events/#event-calendar
 Release candidate by 19th May
 Release on 2nd June

 The documentation is at:

 https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

 I've initialised the release branches already so you won't need direct
 merge access anywhere, you will be able to do any pull requests from forks

 I'll be available to answer any questions and provide guidance (along
 with hopefully other past release leads)

 We chat in #jenkins-release on freenode IRC,
 https://www.jenkins.io/chat/#jenkins-release

 Anyone interested?

 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/8b385b38-4fc5-4efe-83dd-27fc38b8f0can%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> Typed slowly with one finger on my phone. Please forgive any interesting
>> auto-corrections or misunderstanding typos.
>>
>> --
>>
> 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/29KPPeKLgRY/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/CAOxYG4xxb5rB7saCf65o8GKZAXWiqUVpNKfmE3VVgusW1C9neg%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/CAPfivLD0H8z0M1UjZzL8_7kOVKqa%2Bo0XVhWxtTNWhyj8vK3v_g%40mail.gmail.com
> 
> .
>
-- 
Typed slowly with one finger on my phone. Please forgive any interesting
auto-corrections or misunderstanding typos.

-- 
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/CAOxYG4zSRin3xs4gPMjkyRxWkCy%2BF6WOvSNpK0RTfDAqwXni9A%40mail.gmail.com.

Re: bom 807 fails dependency checks in git client plugin

[Tim Jacomb]

Script security should be changed to use the api plugin by the looks of it
to fix that

On Sat, 8 May 2021 at 08:12, Mark Waite  wrote:

> I tried to update the git client plugin to use bom 807.  The update fails
> to compile with a message about the required bounds check failing on the
> caffeine library.
>
> Any suggestions of changes I should make in the git client plugin to use
> the most recent bill of materials?
>
> https://github.com/jenkinsci/git-client-plugin/pull/702 is the pull
> request
>
>
> Mark Waite
>
> --
> 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/64f55a31-4dfa-4ba9-b15e-aca6e7620864n%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-3BidoNO5Y1n5ddVz4z2MaovvJu9VdcxTsLiwSEb1JKQLYSQ%40mail.gmail.com.

bom 807 fails dependency checks in git client plugin

[Mark Waite]

I tried to update the git client plugin to use bom 807.  The update fails 
to compile with a message about the required bounds check failing on the 
caffeine library.

Any suggestions of changes I should make in the git client plugin to use 
the most recent bill of materials?

https://github.com/jenkinsci/git-client-plugin/pull/702 is the pull request

Mark Waite

-- 
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/64f55a31-4dfa-4ba9-b15e-aca6e7620864n%40googlegroups.com.