Re: Kevin Martens as a copy editor for jenkins.io

https://github.com/jenkins-infra/helpdesk/issues/3139 has been opened and completed. Thanks! On Monday, September 19, 2022 at 3:07:03 PM UTC-6 Mark Waite wrote: > Based on all the feedback, as documentation officer I approve Kevin's > membership in the copy editors group. > > I'll open a help

Re: Kevin Martens as a copy editor for jenkins.io

Based on all the feedback, as documentation officer I approve Kevin's membership in the copy editors group. I'll open a help desk ticket to have the infra team add him as a member. On Friday, September 16, 2022 at 11:29:03 AM UTC-6 hle...@cloudbees.com wrote: > +1! > > On Thursday, September

Re: argLine when running integration tests with Java 17

I do not mean the bug that Basil explained in https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.40 This has been fixed already in IntelliJ. IntelliJ now correctly runs the integration tests with an argLine like:

Governance meeting - September 19, 2022

Governance meeting starts in about 60 minutes at 5:00 PM UTC. Agenda items include: Agenda: - News - LTS 2.361.2 release October 5, 2022 - Hacktoberfest is coming, welcome to Preptember - Action items - Mark Waite

Re: argLine when running integration tests with Java 17

Hi Ullrich, There is a known bug in IntelliJ, check out this post on Stackoverflow for the workaround. https://stackoverflow.com/questions/24115142/intellij-error-when-running-unit-test-could-not-find-or-load-main-class-suref Regards, Alex On Mon, Sep 19, 2022 at 2:54 AM Ullrich Hafner

Hacktoberfest Preptember

Hello, As you know, Hacktoberfest starts in two weeks. And the Jenkins community will participate again in this month-long celebration of open-source. As maintainer you can prepare by - Reviewing and flag

argLine when running integration tests with Java 17

I recently switched my development to Java 17 and most things work flawlessly now. One thing that I can’t get to work is debugging of integration tests in IntelliJ. It seems that the argLine command (that opens Java modules) is not sent to the debugging process. However, the same tests run