Re: Plugins using removed Guava APIs

scm-api done in https://github.com/jenkinsci/scm-api-plugin/pull/85 not released On Fri, 7 May 2021 at 03:40, Basil Crow wrote: > I started looking into which plugins use classes or methods from Guava > 11 that have been removed in Guava 30. There is plenty of low-hanging > fruit if anyone is

Re: New BOM version 807.v6d348e44c987 seems out of step with the versioning pattern

That means the maven enforcer will strike back unless all plugins use CD ;-) The frequency of required updates will be an magnitude higher now… > Am 06.05.2021 um 15:56 schrieb Tim Jacomb : > > Yes it's moved to CD releases https://www.jenkins.io/jep/229 > >

Re: New BOM version 807.v6d348e44c987 seems out of step with the versioning pattern

> That means the maven enforcer will strike back unless all plugins use CD ;-) The frequency of required updates will be an magnitude higher now… While bom does use the CD mechanism for release it doesn't actually do 'CD' The releases are triggered either manually or if someone merges a PR with

Looking for release lead for 2.289.1

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:

Re: Plugins using removed Guava APIs

FTR I've removed guava in all maintained azure plugins today (except azure-ad, needs a follow up to move to caffeine cache) Hopefully it's easy to generate your list again, is there a script? On Fri, 7 May 2021 at 11:09, jn...@cloudbees.com wrote: > HI Basil, > > Apologies I said I was going

Re: Plugins using removed Guava APIs

I see you used usage in plugins :) On Fri, 7 May 2021 at 11:14, Tim Jacomb wrote: > FTR I've removed guava in all maintained azure plugins today (except > azure-ad, needs a follow up to move to caffeine cache) > > Hopefully it's easy to generate your list again, is there a script? > > On Fri, 7

Re: Plugins using removed Guava APIs

blueocean is WIP https://github.com/jenkinsci/blueocean-plugin/pull/2163 (please don't create separate PR) On Fri, 7 May 2021 at 12:40, Basil Crow wrote: > I started looking into which plugins use classes or methods from Guava > 11 that have been removed in Guava 30. There is plenty of

Re: New BOM version 807.v6d348e44c987 seems out of step with the versioning pattern

On Fri, May 7, 2021 at 6:12 AM Tim Jacomb wrote: > The releases are triggered either manually or if someone merges a PR with > an 'interesting label' > Background: https://github.com/jenkinsci/jep/blob/master/jep/229/README.adoc#frequency-of-deployments -- You received this message because

Re: Plugins using removed Guava APIs

Thank you for sharing this! I posted PRs for Timestamper and Lockable Resources: https://github.com/jenkinsci/timestamper-plugin/pull/116 https://github.com/jenkinsci/lockable-resources-plugin/pull/242 > I am wondering how best we should co-ordinate this work? I suggest writing some developer

Re: Plugins using removed Guava APIs

> remember is uses a PR not master of usage in plugins so it will find usage in libraries too! I merged usage in plugins this morning, so unless you need it released in some way you shouldn't need that On Fri, 7 May 2021 at 16:07, Basil Crow wrote: > Thank you for sharing this! I posted PRs

Re: Plugins using removed Guava APIs

> Hopefully it's easy to generate your list again, is there a script? > I see you used usage in plugins :) I have a parameterized job I can kick off internally (the main bit being the list of things to pass "usage-in-plugins" which was created from the rev-api report.) attached these if anyone

Re: Plugins using removed Guava APIs

> > I merged usage in plugins this morning, so unless you need it released in > some way you shouldn't need that > Many thanks Tim! On Fri, 7 May 2021 at 16:08, Tim Jacomb wrote: > > remember is uses a PR not master of usage in plugins so it will find > usage in libraries too! > > I merged

Re: Looking for release lead for 2.289.1

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:

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

Hi Tim! I think you and anyone else can start contributing to the plugin without needing any permissions on the JetBrains Marketplace. No objections from me w.r.t. granting these permissions if others agree. On a separate note, should we go ahead and move the repository to the jenkinsci org?

Re: Looking for release lead for 2.289.1

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

Re: Looking for release lead for 2.289.1

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

Re: Looking for release lead for 2.289.1

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