Re: Java 11 as minimum? (Jetty 9.4.x EOL)

> I don't yet see a compelling benefit that would motivate us to drop support for OpenJDK 8. Its support lifetime is almost as long as Java 11. New language features... Not stuck on a version released 7 years ago... Libraries dropping support for it... I'm now sure how the Java 8 baseline

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Wed, Nov 17, 2021 at 4:03 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > […] do not show a rapid growth of Java 11 adoption > > Every time this topic comes up I need to remind people that while the proportion of installations currently running 8 vs. 11 is an

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Wed, Nov 17, 2021 at 12:49 AM Oleg Nenashev wrote: > I think we should eventually drop Java 8 support but only when we have > enough Java 11 adoption About that… https://stats.jenkins.io/plugin-installation-trend/jvms.json seems unlikely given we switched the Docker images around. Even

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Wed, Nov 17, 2021 at 10:03 AM Daniel Beck wrote: > > In fact, looking at the difference between > https://stats.jenkins.io/jenkins-stats/svg/total-jenkins.svg and the JVM > stats, we can see they were almost equal (99+%) up to early 2019. And then > around the time

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

Yes, something is definitely wrong. We have a sync-up with Andrew Bayer today, let's see what whether we could triage that quickly On Wed, Nov 17, 2021 at 10:17 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > > On Wed, Nov 17, 2021 at 10:03 AM Daniel Beck

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

After thinking about the problem in more detail have an additional question: I can replace all of those list modifying operations with a CopyOnWriteArrayList. What is still not clear for me is, how this works if multiple objects are affected? E.g. I have a loop over a number of files that

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

> So it's almost certain we're just not collecting usage stats correctly. Filed https://issues.jenkins.io/browse/JENKINS-67158 for investigation, would be great if someone can take a look! On Wed, 17 Nov 2021 at 09:03, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote:

Re: Enabling Continuous Delivery / automated release process for Gradle project

I don't think it will have been done yet because the GitHub actions only support maven. There's not many projects using gradle so I guess you're the first to look at it. The action wouldn't need much work to support it, Probably just a flag defaulted to maven and then a change in this script:

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

On Wed, Nov 17, 2021 at 5:57 AM Ullrich Hafner wrote: > […] is stored in a CopyOnWriteArrayList. If your background thread > serializes my instance during the loop it can happen that the loop variable > is already set, but the list with the results is not. > Hard to follow what you are saying

Enabling Continuous Delivery / automated release process for Gradle project

Hey folks, I saw https://groups.google.com/g/jenkinsci-dev/c/4o75QPEslyU and https://www.jenkins.io/doc/developer/publishing/releasing-cd/ and was very interested in setting it up for the Job DSL Plugin , but it's a Gradle project. Has anyone set

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Wed, Nov 17, 2021 at 4:05 AM Tim Jacomb wrote: > That's assuming that the gradle plugin supports incrementals which I don't > know if it does. > It does not, and the whole concept is rather specific to Maven. Stepping back, there are basically two sides to JEP-229: a backend patch to the

Governance meeting Nov 17, 2021

The draft agenda for today's governance meeting is: - News - Jenkins 2.321 has released - Jenkins 2.319.1 release candidate has arrived - Jenkins infrastructure costs reducing, likely within budget - Election status report - Highlights from the mailing lists and

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

> As far as I understood the problem in JENKINS-67145 my step is somehow serialized during the execution in lines 205-215. Kind of, but I was talking about the publishIssues step, not the scanForIssues step. I think the scanForIssues steps in the

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

> Am 17.11.2021 um 16:36 schrieb 'Devin Nusbaum' via Jenkins Developers > : > > > As far as I understood the problem in JENKINS-67145 > > my step is somehow > > serialized during the execution in lines 205-215. > > Kind of, but I was talking

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

> Am 17.11.2021 um 14:42 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Wed, Nov 17, 2021 at 5:57 AM Ullrich Hafner > wrote: > […] is stored in a CopyOnWriteArrayList. If your background thread serializes > my instance during the loop it can happen

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

On Wed, Nov 17, 2021 at 10:02 AM Ullrich Hafner wrote: > I do not have fields anymore in the step > > Any class which could be referenced directly or indirectly as part of the program state (object graph rooted in Pipeline virtual threads) must be written to expect concurrent access from a

Re: New members of jenkins.io triage team

We met in Docs Office Hours this week and decided that we should proceed to add the new members to the triage team even without the new CLA process. On Thu, Nov 4, 2021 at 10:41 AM Mark Waite wrote: > +1 from me to enable EasyCLA for the > https://github.com/jenkinsci/infra-cla repository . > >

Re: New members of jenkins.io triage team

+1 no need for triage, it doesn't give much permission at all On Wed, 17 Nov 2021 at 16:16, Mark Waite wrote: > We met in Docs Office Hours this week and decided that we should proceed > to add the new members to the triage team even without the new CLA process. > > On Thu, Nov 4, 2021 at 10:41

Jenkins 2.319.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. The final release is scheduled for 2021-11-01 Please, report your findings in this thread. Download the release from

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

Agreed that the benefit to developers is a critical point. For Java 8 bump that was a big driver. We do want Jenkins to be appealing to the OSS Java developers out there. I think we should plan & announce ahead like we've