Re: What's i18n message key string case style is recommend?

[Mark Waite]

On Thursday, May 16, 2024 at 9:21:47 PM UTC-6 Bob wrote:

What's i18n message key string case style is recommend?

I've reviewed the current i18n message key string case style conventions.
In the core, it is already in a very chaotic state.
Not to mention in various plugins.

some file use PascalCase
like: core/src/main/resources/hudson/cli/Messages.properties

some file use camelCase
like: core/src/main/resources/jenkins/console/Messages.properties

some file use snake_case
like: 
core/src/main/resources/hudson/model/Cause/UserIdCause/description.properties

some file even mix under_score and CamelCase naming conventions.
like: core/src/main/resources/jenkins/install/Messages.properties

If there were no previous conventions regarding this matter, can we reach a 
new consensus on which naming style to use in new files?
To be honest, every time I need to add a new message key, I hesitate for 
quite some time.


I believe there were no conventions previously because the initial default 
is to use a form of the original message text as the name of the property.

I prefer the camel case format because the properties are fields of their 
associated Messages class in Java.
 
I prefer to not change the existing property names due to the risk of 
mistakes and surprises from that type of renaming exercise.

I'm open to other ways of thinking

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/8517e0fd-79cb-4ff1-aaab-417cf4ad1990n%40googlegroups.com.

Re: 2.452.2 Release Lead

[Mark Waite]

Thanks very much!

On Thursday, May 16, 2024 at 5:14:22 AM UTC-6 kris...@outlook.com wrote:

> Hi everyone,
>
> I volunteer to be the Release Lead for the upcoming LTS 2.452.2. 
>
> The Release Candidate is scheduled for May 29th, 2024, and the Final 
> Release for June 12th, 2024.
>
> Best,
> Kris 
>
>

-- 
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/5009c649-d3b7-43ac-bb3a-e51e8febb0e4n%40googlegroups.com.

May 13, 2025 Governance Board Agenda

[Mark Waite]

Governance meeting starts today at 6:00 PM UTC.  Zoom link 
is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Draft agenda is available at https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view 
and includes topics:

   - Jenkins in Google Summer of Code
   - Accelerating weekly requirement for Java 17
   - Azure expense status
   - AWS expense status
   - Proposal to cancel next governance meeting due to U.S. public holiday

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/22656e3a-e3b0-473a-9f24-4ef9dd9b7529n%40googlegroups.com.

Re: Spring Security upgrade from 5.x to 6.x

[Mark Waite]

On Friday, May 10, 2024 at 12:51:46 PM UTC-6 Basil wrote:

Based on my prototyping in JENKINS-73120, there is quite a bit of work 
to support Jetty 12 (even just EE 8 with javax imports), blocked on 
the requirement of Java 17. From my perspective the sooner we require 
Java 17, the better. Perhaps we can require Java 17 in weeklies two 
weeks earlier than planned, acknowledging that this creates two fewer 
choices for LTS selection. Thoughts? 


I like the idea.  It would mean that the LTS baseline selected for the
last Jenkins LTS to support Java 11 would need to be two weeks earlier,
but we've chosen LTS baselines that were not the most recent weekly
before.

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/450e7eff-2c7b-4aba-a10a-979aa7dba9a2n%40googlegroups.com.

April 29, 2024 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 6:00 PM UTC today.  Zoom link 
is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Draft agenda is available at https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view 
and includes topics:

   - Trademark approval request - Jenkins as a Service by CloudBees
   - Azure expense status
   - AWS credits donation
   - Spring Security 5.8.x end of public support

-- 
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/67949990-f5e3-4b91-91f9-60124c174bb4n%40googlegroups.com.

Re: Plugin with Java 17 minimum dependencies

[Mark Waite]

On Sat, Apr 27, 2024 at 1:24 AM Valentin Delaye (jonesbusy) <
jonesb...@gmail.com> wrote:

> Hi,
>
> I'm a bit confused on the minimum required Java version for plugins
>
> I maintain the https://github.com/jenkinsci/flyway-api-plugin which is an
> API plugin for flyway dependencies.
>
> Since flyway 10 Java 17 is required.
>
> I open a PR https://github.com/jenkinsci/flyway-api-plugin/pull/9/files
>
> And changing the
>
> 17  .compiler.testRelease>17
>
> And tested using bom the plugin against known consumer. No issue found
>
> However is looks I cannot release the plugin
> https://github.com/jenkinsci/flyway-api-plugin/actions/runs/8858031719/job/24326194647
> due to JDK11 used on CD.
>
> - Is it expected ?
>

Yes, that's expected because no Jenkins core version requires Java 17 as
its minimum Java version.


> - Does this mean the plugin need a Java 17 runtime or only for compile ?
>

I believe that when you set maven.compiler.release to 17, it is generating
Java 17 byte code.  That will require Java 17 at runtime.


> - Show I rollback until the toolchain is adapted for Java 17 ?
>

I would rollback until the toolchain supports Java 17 later this year.  It
might be in the weekly release as early as July or August.

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/CAO49JtEF1R%3DP52_%2BBQaDKLoD8ymByv_5jB54E1J4ambyM7PftA%40mail.gmail.com.

Re: Missing publication of plugin oic-auth releases in maven repository

[Mark Waite]

On Sunday, April 21, 2024 at 9:57:07 AM UTC-6 Michael wrote:

  Thanks for the clarification.

IIU it means that if I see a package in jenkins'artificatory it is avaible 
as a maven package ; mvnrepository just doesn't pick it up for whatever 
reason.
https://repo.jenkins-ci.org/ui/packages/gav:%2F%2Forg.jenkins-ci.plugins:oic-auth?name=oic-auth=packages

I was wondering why the card in plugins site was still showing the 1 year 
old (2.6) version:
https://plugins.jenkins.io/ui/search/?query=oic-auth
And got side tracked by this mvn repository not showing more recent 
versions.


The plugins.jenkins.io site takes from 3-6 hours to detect a new release of 
a plugin.

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/eb2d31f6-aa1d-49f8-8290-50ae549f6a22n%40googlegroups.com.

Re: 2.452.1 release lead

[Mark Waite]

On Saturday, April 20, 2024 at 1:14:09 AM UTC-6 Alexander Brandes wrote:

Hey everyone,

I am volunteering to be the release lead for the upcoming LTS release, 
2.452.1

The RC is scheduled for the 1st of May, final release for the 15th of May.


Thanks very much!  +1 from me

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/3b1821f2-d1f0-4dc2-b580-d8ad53f0907an%40googlegroups.com.

Re: April 15, 2024 Governance Board Agenda

[Mark Waite]

Zoom link 
is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

On Monday, April 15, 2024 at 7:50:41 AM UTC-7 Mark Waite wrote:

> The Jenkins board meeting starts at 6:00 PM UTC today.  Zoom link is 
>
> Draft agenda is available at https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view 
> and includes topics:
>
>- Azure expense status
>- AWS credits donation
>- Spring Security 5.8.x end of public support
>
> 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/b61e5bc6-1534-4cbf-8f8d-1eef1d3890a4n%40googlegroups.com.

April 15, 2024 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 6:00 PM UTC today.  Zoom link is 

Draft agenda is available at https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view 
and includes topics:

   - Azure expense status
   - AWS credits donation
   - Spring Security 5.8.x end of public support
   
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/541877cb-c388-4c05-99f8-523ccce89980n%40googlegroups.com.

2.452 as May 15, 2024 LTS baseline?

[Mark Waite]

We should select the baseline today for the long term support release that 
will be delivered May 15, 2024.

I propose Jenkins 2.452 <https://www.jenkins.io/changelog/#v2.452> as the 
next LTS baseline.  It was released yesterday Apr 3, 2024.

Feedback is positive on the release.  It is running on weekly.jenkins.io and 
I'm using on my weekly installation.  The last 10+ weekly releases have 
good ratings with no serious open regressions.

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/f4607e94-03cd-433c-9fe2-ce9efbb24482n%40googlegroups.com.

Re: Adopt msbuild plugiin

[Mark Waite]

This is great.  Thanks very much for adopting the plugin!

On Tuesday, April 2, 2024 at 9:53:14 AM UTC-6 tilalx wrote:

> Hi,
>
> the msbuild plugin is up for adoption. I'd like to adopt it in order to 
> deliver some features.
>
> plugin pull request: https://github.com/jenkinsci/msbuild-plugin/pull/118 
> RPU pull request: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3868
> GitHub username: tilalx
> Jenkins username: tilalx
>
> Regards,
> Tilo
>

-- 
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/0b02657d-4e25-4027-b9c2-0590bc4cc4dan%40googlegroups.com.

Re: Create an empty plugin template

[Mark Waite]

On Wednesday, March 27, 2024 at 10:39:32 PM UTC-6 Owen wrote:

No gradle instructions?? Not being a purist or anything but many will have 
these instructions side by side.


Jenkins plugin development tools are focused on Apache Maven.  We have a 
very small set of plugins that are maintained with gradle.  Those plugins 
struggle to keep pace with the tool changes that are made in the Apache 
Maven tooling.

We don't post a "Create a plugin" tutorial based on Gradle.  We don't have 
a tutorial based on Gradle.

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/973dac21-e308-40cb-97e9-5b79d82acb17n%40googlegroups.com.

Spring Security upgrade from 5.x to 6.x

[Mark Waite]

The Spring project has announced that Spring Security 5.8.x and Spring 
Framework 5.3.x will be end of life on August 31, 2024 
<https://spring.io/blog/2024/03/01/support-timeline-announcement-for-spring-framework-6-0-x-and-5-3-x>.
  
Jenkins currently uses  Spring Security 5.8.x and Spring Framework 5.3.x.

Jenkins needs to upgrade to Spring Security 6.x.  Spring Security 6.x in 
Jenkins requires:

   - Spring Framework 6.x which requires Java 17 and Jakarta EE 9 
   
<https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-Versions#jdk-version-range>

When Jenkins transitions from Jakarta EE 8 to Jakarta EE 9, we'll also need 
to use:

   - Jetty 12
   - Apache file uploader 2.x

Given the size of that change and its dependency on Java 17 as a minimum 
Jenkins version, I think that we want to switch Jenkins to require Java 17 
as soon as possible after the last Java 11 LTS baseline is selected.

*Proposed Timeline*

   - 26 Jun 2024 - Choose LTS baseline for last LTS to support Java 11
   - 3 Jul 2024 - Require Java 17 in Jenkins weekly release
   - 7 Aug 2024 -Last LTS.1 release to support Java 11 (likely 2.464.1)
   - 31 Aug 2024 Spring Security 5.8.x public support ends
   - 18 Sep 2024 - Choose LTS baseline to require Java 17
   - 2 Oct 2024 - Last LTS.3 to support Java 11
   - 30 Oct 2024 - First LTS.1 to require Java 17 (likely 2.476.1)

Basil prototyped the Jakarta EE 9 upgrade in August 2023.  The prototype 
showed that the bridge method injector may help with the transition.  The 
prototype showed that there is a lot of work to be done in order to upgrade 
Spring Security in Jenkins from 5.x to 6.x

I noted the timeline because I had initially assumed that we would 
transition Jenkins weekly to require Java 17 in late August or early 
September 2024.  Based on the large amount of work that is needed for the 
Spring Security upgrade from 5.x to 6.x, I think that we should require 
Java 17 the week after we've selected the baseline for the final LTS line 
that will support Java 11.

If you're willing to help with the Spring Security upgrade project, I'd 
love to have you respond to this email message.  If you have strong 
objections to the timeline, please respond with your concerns.

I will share more details as I learn more.

Thanks,
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/4a260cec-dbe4-4b63-a9e6-7c17ebcbfaebn%40googlegroups.com.

Re: Adopt email-ext plugin

[Mark Waite]

+1 from me

On Thu, Mar 28, 2024 at 9:59 AM Alex Earl  wrote:

> Howdy,
>
> The email-ext plugin is up for adoption. I'd like to re-adopt it (been a
> few years so I may be a little rusty :) )
>
> RPU pull request:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3851
> 
> GitHub username: slide (already member of jenkinsci organization)
> Jenkins username: slide_o_mix
>
> Thanks
>
> Alex
>
> --
> 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/ee3bd5a5-ca18-4642-94c5-3a3b83640515n%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/CAO49JtEZ-MZzB_84E8aYPd2Bqce_vW6%3D_j6EbVkf%2B7HNjkiDUQ%40mail.gmail.com.

Re: Create an empty plugin template

[Mark Waite]

On Wednesday, March 27, 2024 at 9:51:51 PM UTC-6 Curtis Babbie wrote:

Hello,

I'm trying to start a new Jenkins plugin project and was hoping to create 
an empty plugin template to which I could start my development work.  I was 
following the development documentation and attempted to select the 
archetype: empty-plugin but it doesn't appear to work.

Please advise any other options or recommendations


"It doesn't appear to work" is very difficult to diagnose.   You'll need to 
provide more details of what you tried to do and what were the results.

Using Apache Maven 3.9.6 and Eclipse Temurin Java 21.0.2 I was able to 
create an empty plugin by following the instructions from the Creating a 
new plugin page 
<https://www.jenkins.io/doc/developer/publishing/new-plugin/>.  The 
commands that I ran were:

mvn archetype:generate -Dfilter=io.jenkins.archetypes:empty-plugin

I answered the prompts as noted in the Create a plugin tutorial 
<https://www.jenkins.io/doc/developer/tutorial/create/>.  The resulting 
plugin compiled and passed its automated tests.

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/922724f3-1850-4985-9d9f-7aa5cd15e73dn%40googlegroups.com.

Re: XGuardian plugin - CI Jenkins

[Mark Waite]

On Monday, March 25, 2024 at 1:16:23 PM UTC-6 Raveli wrote:

Hello, I have a plugin called XGuardian for automatically zip the workspace 
and upload the source code for the Xguardian platform and I would like it 
to be forked on github.

https://github.com/xmart-xguardian/plugin-jenkins


Thanks for your interest.  
https://www.jenkins.io/doc/developer/publishing/requesting-hosting/ 
provides the list of steps needed to host a plugin in the Jenkins project. 

-- 
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/e268ac79-d4d3-448d-b4eb-39c0ee0944e5n%40googlegroups.com.

March 18, 2024 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).  
Zoom  link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda: 


News 


   - Ampere Computing loaner AMR64 server is running Jenkins tasks
   - Jenkins has been accepted to Google Summer of Code 2024, see Blog post 
    from 
   Alyssa Tong
  - Proposols to be sent by end of March
   - Jenkins award voting is in progress. These awards recognize 
   contributions from individuals in the community and the progress made in 
   the name of Jenkins. Nominated candidates are:
  - Most Valuable Jenkins Advocate:
 - Alexander Brandes
 - Bruno Verachten
 - Darin Pope
 - Kris Stern
  - Most Valuable Jenkins Contributor:
 - Basil Crow
 - Daniel Beck
 - Kris Stern
 - Stefan Spieker
 - Tim Jacomb
 - Ullrich Hafner
  - Jenkins Security MVP:
 - Alvaro Muñoz
 - Yaniv Nizry
  - Voting 
  

 is 
  possible until March 22, 2024
   
Action Items 


   - Basil create the attribution entries for the downloads page
  - Jenkins sponsors have changed
  - Draft PR is almost ready for review at: 
  jenkins-infra/jenkins.io#6882 
  
   - Kevin Martens retire the Chinese Jenkins site
  - Mark needs to do more Kubernetes setup, then Kevin and Mark will 
  meet with Damien
  - More work after Kevin returns from holiday
   
Community activity 


   - GSoC preparation: A lot of traffic in the community forums, chat 
   rooms, and GitHub repositories
   - Contributer Spotlight this week: Bruno Verachten

Governance Topics 


   - Azure expense status
  - February expenses were $4200 USD - nicely under $5000 budget
 - Special thanks to Damien, Herve, and Stephane for cost reductions
  - AWS credits donation
  - Credits have been received, not yet applying credits to Jenkins 
  tasks
   - Delphix plugin uses a proprietary component 
   
  - Delphix maintainers have proposed an idea for the fix
  - Thanks to @daniel-beck for finding the issue and working with 
  Delphix plugin maintainers
   - Java 11 end of life and Spring end of public support 
   

  - Last public build of Spring security framework 5.8.x is August 2024
 - Spring security 6.x requires Jetty 11 with Jakarta EE 9 
 (jakartaee.servlet), not Jetty 10 with Jakarta EE 8 (javax.servlet)
  - Last public build of Spring framework 5.3.x is August 2024
 - Spring framework 6.1 and later require Java 17
  - Alternatives:
 - Accept that if there is a security vulnerability reported in 
 Spring security 5.8.x between August 2024 and end Oct 2024, we may 
need to 
 fork Spring Security and fix it ourselves
  

-- 
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/31a9639c-746c-4691-8f7f-a15973a8fa90n%40googlegroups.com.

Re: jenkins-2.440.2-rc has been released

[Mark Waite]

I've been running the 2.440.2 release candidate for at least a week without 
any issues.

On Thursday, March 7, 2024 at 11:20:53 PM UTC-8 jenkinsr...@gmail.com wrote:

> Please report issues found to the release candidate announcement 
>  
> thread.
>
> Final release is scheduled for *2024-03-20*.
>
> Download the release from: 
> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.440.2-rc34558.57a
> *b*5503a*255/jenkins-war-2.440.2-rc34558.57a*b*5503a*255.war 
> 
>
> After final release, the official changelog 
>  and official upgrade 
> guide 
> 
>  
> will be available on www.jenkins.io/download.
>

-- 
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/dbfbcc6c-22dd-4aa9-bfb1-eba6236ff76an%40googlegroups.com.

Re: Remove Suggestimate from issues.jenkins.io?

[Mark Waite]

On Monday, March 11, 2024 at 10:00:25 AM UTC-6 Tim wrote:

According to their website it's free for open source projects:
https://enhancera.com/jira/suggestimate/buy.html


Thanks for that link.  I'm not sure what the "standard Atlassian procedure" 
for an open source license is, especially since we're using a Jira 
Datacenter license and I believe that most open source projects are using 
Jira cloud.

The Linux Foundation administrator has renewed the licenses for the two 
Jira plugins with expired licenses.  We can consider this closed, since the 
plugin license is renewed.
 

I think it's just in a bit of a state of confusion due to Atlassian's 
retirement of server and our moving to data center.

Is it worth trying to get the plugin relicensed, e.g. does it provide 
benefit by preventing some duplicate tickets being filed?


I've personally not seen any benefit from it, but I'm not a representative 
sample of Jenkins issue submitters.  I plan to leave the plugin as it is, 
installed and available on issues.jenkins.io

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/dbdb5e62-690d-4dec-aae2-205872cb1448n%40googlegroups.com.

Remove Suggestimate from issues.jenkins.io?

[Mark Waite]

The Jenkins Jira instance <https://issues.jenkins.io> uses a Jira 
datacenter license that is donated to the Jenkins project by Atlassian.

The Suggestimate plugin 
<https://marketplace.atlassian.com/apps/22805/suggestimate-for-jira?tab=overview=datacenter>
 
is installed on the Jenkins Jira instance and is reporting that its license 
has expired.  The Suggestimate pricing page 
<https://marketplace.atlassian.com/apps/22805/suggestimate-for-jira?tab=pricing=datacenter>
 
says that the plugin would cost $4500 per year based on the number of users 
of our Jira instance.  The question and answer section indicates that our 
donated Jira Datacenter license does not include the license for the plugin.

I propose that we should remove that plugin from issues.jenkins.io rather 
than pay a licensing fee for the plugin.

Any objections to the removal of that plugin from issues.jenkins.io?

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/a96f9c00-ff28-47fb-a3eb-210826ae5d7dn%40googlegroups.com.

Re: Jira upgrade Mar 12, 2024 at 23:00 UTC

[Mark Waite]

On Tuesday, February 20, 2024 at 4:44:25 PM UTC-7 Mark Waite wrote:

I've proposed a Jira upgrade with a maintenance window of 3 hours for 
Tuesday, March 12, 2024 beginning at 23:00 UTC.  

https://github.com/jenkins-infra/status/pull/474 is the pull request 
proposing the maintenance.  

https://github.com/jenkins-infra/helpdesk/issues/3939 is the helpdesk 
ticket that initiated the request.


The Linux Foundation status page for the upgrade 
is https://status.linuxfoundation.org/incidents/d6c890x0lrlp

-- 
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/190763cb-2549-441f-823f-e25d4c4acf69n%40googlegroups.com.

Jira upgrade Mar 12, 2024 at 23:00 UTC

[Mark Waite]

I've proposed a Jira upgrade with a maintenance window of 3 hours for 
Tuesday, March 12, 2024 beginning at 23:00 UTC.  

https://github.com/jenkins-infra/status/pull/474 is the pull request 
proposing the maintenance.  

https://github.com/jenkins-infra/helpdesk/issues/3939 is the helpdesk 
ticket that initiated the request.

Reply to this message or in one of those two GitHub locations if that date 
and time are a problem.

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/3ca150be-5c87-437b-a031-b2c0918dd6dan%40googlegroups.com.

Re: Proposal: Remove inactive core-pr-reviewers from the team

[Mark Waite]

On Monday, February 19, 2024 at 1:18:57 PM UTC-7 Alexander Brandes wrote:

Hey everyone,

While onboarding Stefan Spieker into the core-pr-reviewers team 
<https://github.com/orgs/jenkinsci/teams/core-pr-reviewers>, I noticed a 
plenty of inactive members in the team, who haven’t engaged with core in 
years.

The team grants triage permission to set labels and update changelog 
entries in Jenkins core and is largely used for notifications in core PRs 
directly.
To maintain an active team, whose members actively engage with core PRs and 
respond to requested reviews, I would propose to remove team members, who 
have not interacted with core within one year.


I am +1 for the idea of removing individuals from the team who have not 
interacted with core in a year or more.

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/95cb3942-cb7f-4179-90cd-01a6345afea9n%40googlegroups.com.

February 19, 2024 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).  
Zoom  link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda: 

News

   - Ampere Computing <https://amperecomputing.com/> has lent 2 servers to 
   the Jenkins project
  - Special thanks
 - Bruno Verachten arranged the loan to the Jenkins project
 - Aaron Williams <https://www.linkedin.com/in/aaron-don-williams/> 
arranged 
 the loan from Ampere Computing
     - Mark Waite is hosting the machines at his house (donating 
 electricity and networking)
 - CloudBees will be asked to donate disc drives and other 
 components as needed
  - Next generation of the Jenkins project involvement with ARM64
 - Oracle Cloud confirmed in 2021 
 
<https://blogs.oracle.com/cloud-infrastructure/post/arm-based-cloud-computing-is-the-next-big-thing-introducing-arm-on-oracle-cloud-infrastructure>
 that 
 Jenkins works well with ARM64
 - Jenkins infrastructure continues transition to ARM64 servers 
 
<https://github.com/jenkins-infra/helpdesk/issues?q=is%3Aissue+is%3Aopen+ARM64>
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Basil create the attribution entries for the downloads page
  - Jenkins sponsors have changed
 - DigitalOcean donated over $20k USD last year and has donated 
 $20k in 2024
 - AWS donation request has been submitted. Answer in 30 days. If 
 no donation, then should remove AWS from root page 
 <https://www.jenkins.io/>
  - Kevin Martens retire the Chinese Jenkins site
  - Mark needs to do more Kubernetes setup, then Kevin and Mark will 
  meet with Damien
  - More work after FOSDEM
   - Stefan Spieker to join the core-pr-reviewer team: 
   https://groups.google.com/g/jenkinsci-dev/c/Wkhrs3nNEEU @NotMyFault 
   <https://hackmd.io/@NotMyFault>
  - Per the maintainer's doc, the board can vote on the decision: 
  
https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#ladder
  - @NotMyFault <https://hackmd.io/@NotMyFault> is in favor, he has 
  been a great help reviewing core PRs and contributing to core before
  - @MarkEWaite is in favor
  - @basil is in favor
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - Contributor summit results
  - Slides 
  
<https://docs.google.com/presentation/d/1teDDAY41zRU9ubbuQw1LMc_W3vf4eNJX8zoUGn7lNSA/edit?usp=sharing>
 from 
  the summit
  - @kmartens27 preparing a summary blog post
  - @MarkEWaite extend the Java 2+2+2 support plan JEP 
  <https://github.com/jenkinsci/jep/pull/400> with results from summit
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - Contributor summit provided additional information
 - HPI plugin has been extended to prepare for Java 11 end of life 
 - PR-578 <https://github.com/jenkinsci/maven-hpi-plugin/pull/578> from 
 Vincent Latombe
- HPI plugin not yet released with the change
 - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Mark has much more work to do here
   - Dropping support for a Java version (refer to Java 11 for 
   ideas)
   - Adding a Java version (use Java 21 addition as the pattern)
   - Making a Java version the recommended version (use Java 17 
   as the pattern)
- Further refinements to be done in the JEP
 - Key dates
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
Topics
   
   - Jenkins awards - Mark Waite
  - Nominations close today, 19 Feb 2024
  - Overview of the Jenkins awards
 - CDF hosts the nominations
 - Most valuable advocate 
 <https://github.com/jenkins-infra/jenkins.io/issues/7030> - 
 speaking, promoting, training, tutoring
 - Most valuable contributor 
 <https://github.com/jenkins-infra/jenkins.io/issues/7028> - 
 features, fixes, and more
 - Security MVP 
 <https://github.com/jenkins-infra/jenkins.io/issues/7029> - 
 security reports and fixes for security issues
  - Nomination process for Jenkins awards
 - Nomination through GitHub issues
- Most valuable advocate 
&

Re: CI problem

[Mark Waite]

On Monday, February 19, 2024 at 8:42:37 AM UTC-7 Michael wrote:

Hi all 

I'm getting some problem on verification build 
16:39:14 Cannot contact jnlp-maven-17-wxw3t: 
hudson.remoting.ChannelClosedException: Channel 
"hudson.remoting.Channel@583d05db:JNLP4-connect connection from 
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039": 


We use spot instances for many of our builds with automatic retry if a spot 
instance is reclaimed by the cloud provider.  That can result in agent 
failures, though they should retry automatically.

One the GitHub checks page 
, you should see 
a "Re-run" action that will allow you to start a ci.jenkins.io job again.

-- 
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/0517b5cb-535d-48ec-b1ed-2ae0e0654e9cn%40googlegroups.com.

Re: Proposal: Stefan Spieker to join the core PR reviewers team

[Mark Waite]

On Sunday, February 18, 2024 at 9:30:35 AM UTC-7 Alexander Brandes wrote:

Hey everyone,

I would like to propose Stefan Spieker (@StefanSpieker 
<https://github.com/StefanSpieker>) to join the core PR reviewers team.

Stefan has been a core contributor since October 2022, and filed 172 
<https://github.com/jenkinsci/jenkins/pulls?q=is:pr+author:stefanspieker> pull 
requests, where 171 PRs have been merged.
Additionally, he has been active in reviewing core PRs and has voiced his 
opinion in almost 300 
<https://github.com/jenkinsci/jenkins/pulls?q=is:pr+reviewed-by:stefanspieker> 
pull 
requests.

I would welcome him as an addition to the core pr team :)


+1 from me.

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/28e931e5-26e9-47c4-80c7-87871a4a929en%40googlegroups.com.

Re: Adopt plugin openid-plugin

[Mark Waite]

On Sunday, February 18, 2024 at 1:42:00 PM UTC-7 Michael wrote:

Hi 

Solved this way 

+  
+ org.jenkins-ci.plugins 
+ junit 
+ 1119.1121.vc43d0fc45561 
+ test 
+  
+  
+ org.jenkins-ci.plugins 
+ script-security 
+ 1175.v4b_d517d6db_f0 
+ test 
+  

Is this the correct way?


That is a valid way to solve it, though most plugin maintainers prefer to 
let the plugin bill of materials manage the versions of dependencies when 
they are available from the plugin bill of materials.

The "Improve a  plugin" tutorial 
<https://www.jenkins.io/doc/developer/tutorial-improve/> includes a section 
on using the plugin bill of materials 
<https://www.jenkins.io/doc/developer/tutorial-improve/use-plugin-bill-of-materials/>
.

It also has a section on updating the minimum Jenkins version 
<https://www.jenkins.io/doc/developer/tutorial-improve/update-base-jenkins-version/>
 
(you probably want 2.414.3 rather than 2.410).

It also has a section on updating the parent pom 
<https://www.jenkins.io/doc/developer/tutorial-improve/update-parent-pom/> 
that will allow you to run tests with Java 21 and Java 17 
<https://www.jenkins.io/doc/developer/tutorial-improve/add-a-jenkinsfile/> 
so that you're confident the plugin works on all the JDKs that Jenkins 
supports.

Thanks very much for adopting the plugin!

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/ca8c242d-1f6d-4ba8-aad6-fe28a29ed6b0n%40googlegroups.com.

Re: Build p4-plugin using gradle.

[Mark Waite]

I agree with Alex.  If you choose to transition from a maven based build to 
a gradle based build, you are also choosing extra work for yourself because 
you will need to track the improvements that are made in the maven build 
process.  It seems like that will be more work than you want to do.

Mark Waite

On Tuesday, February 13, 2024 at 6:54:21 AM UTC-8 Alexander Brandes wrote:

> > Any insights or suggestions
>
> I would suggest staying with the maven toolchain, given the JPI plugin is 
> feature stalled and we stopped onboarding plugins using Gradle over Maven 
> more than a year ago.
> If loss of functionality, stability, and support is no concern, you may 
> use Gradle.
>
> On 13. Feb 2024, at 10:02, Sandeep Kumar  wrote:
>
> Hi Team,
>
> In the p4-plugin, I have made the switch from Maven to Gradle as the build 
> tool using "gradle-jpi-plugin" (
> https://github.com/jenkinsci/gradle-jpi-plugin).
>
> Before publishing, I want to gather feedback from the community to address 
> any potential issues that may have been overlooked during this migration. 
>
> The Gradle file for the plugin can be found here: 
> https://github.com/jenkinsci/p4-plugin/blob/master/build.gradle. Any 
> insights or suggestions from the community would be highly appreciated.
>
> Also, Which repository should be prioritized for publishing artifacts: 
> https://repo.jenkins-ci.org/public/ or 
> https://repo.jenkins-ci.org/releases?
>
> P4-Plugin: https://github.com/jenkinsci/p4-plugin
>
> Thanks
> Sandeep Kumar
> sku...@perforce.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/1e67637a-6da6-499e-9e0c-5c746d746ff6n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/1e67637a-6da6-499e-9e0c-5c746d746ff6n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

-- 
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/604d00da-6812-4173-808d-3f0225a1775bn%40googlegroups.com.

Re: Jenkins 2.440.1-rc has been released

[Mark Waite]

On Thursday, February 8, 2024 at 5:47:35 AM UTC-7 Alexander Brandes wrote:

Hey everyone,

Jenkins 2.440.1 RC has been released and is ready to be tested.

Please report issues found in this thread.

The final release is scheduled for 21.02.2024.

Download the release candidate from artifactory: 
https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/jenkins-war/2.440.1-SNAPSHOT/jenkins-war-2.440.1-20240208.123517-1.war
 


I'm using it in my test environment and have found no issues yet.
 
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/ec73d542-7e79-4456-9cc6-6147712a6a02n%40googlegroups.com.

Re: Adopt request for Nexus Artifact Uploader

[Mark Waite]

On Thursday, February 1, 2024 at 8:23:08 PM UTC+1 Veera wrote:

Hi Team,

Please provide the Nexus Artifact Uploader plugin for my self practice 
purpose.


That's not enough information in order for you to adopt a plugin.  Please 
follow the instructions on the "Adopt a plugin" page 
<https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/>. 

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/a72ec214-3589-4d34-aa4f-561cb43a3c99n%40googlegroups.com.

January 22, 2024 Governance Board Agenda

[Mark Waite]

*News*

   - Wednesday Jan 24, 2024 security release 
   <https://groups.google.com/g/jenkinsci-advisories/c/QZiecB2ArMs> of both 
   weekly and LTS versions
  - Merges to Jenkins core are intentionally blocked to avoid 
  disrupting that release
  - Security advisory will be published the day of the release
   - Docker sponsorship of Jenkins project continues (controllers, agents, 
   and containers for infrastructure)

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Basil create the attribution entries for the downloads page
  - Jenkins sponsors have changed
 - DigitalOcean donated over $20k USD last year and has donated 
 $20k in 2024
 - AWS donation request has been submitted. Answer in 30 days. If 
 no donation, then should remove AWS from root page 
 <https://www.jenkins.io/>
  - Kevin Martens retire the Chinese Jenkins site
  - Mark needs to do more Kubernetes setup, then Kevin and Mark will 
  meet with Damien
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - 
   
   Contributor Summit Feb 2, 2024 in Brussels
   - Over 20 confirmed attendees, including 4 of 5 board members and most 
  Jenkins officers
  - Jean-Marc Meessen is coordinating the agenda 
  
<https://community.jenkins.io/t/jenkins-contributor-summit-on-feb-2-2024-call-for-topics-and-ideas/10689>
  - Draft agenda proposal 
  
<https://community.jenkins.io/t/jenkins-contributor-summit-2024-update/11794>
   includes:
 - Board and officer reports and look to the future
- Board report - a board member
- Infrastructure report - Damien Duportal
- Release officer report - Tim Jacomb(?) or Mark Waite
- Docs officer report - Kevin Martens
- Events officer report - Alyssa Tong
- Security officer report - Wadeck Follonier
- User experience SIG report - Tim Jacomb(?) or Mark Waite
 - Changes in Jenkins for HA/HS support - Vincent Latombe
 - Blue Ocean deprecation prep - Alex Brandes & Damien Duportal
 - User experience evolution - Tim Jacomb(?) or Mark Waite
 - Searching the code with the “usage in plugins” tool - Basil Crow
 - Jenkinsfile Runner update - Oleg Nenashev
 - Java support plan - Mark Waite
  - Submit agenda suggestions to community.jenkins.io 
  
<https://community.jenkins.io/t/jenkins-contributor-summit-on-feb-2-2024-call-for-topics-and-ideas/10689>
   - 
   
   Java 11, 17, and 21 in Jenkins - Mark Waite
   - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Mark has much more work to do here
   - Adding a Java version (use Java 21 addition as the pattern)
   - Making a Java version the recommended version (use Java 17 
   as the pattern)
   - Dropping support for a Java version (refer to Java 11 for 
   ideas)
- Further refinements to be done in the JEP
 - Key dates
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
Topics
   
   - 
   
   Jenkins awards - Alyssa Tong
   - Overview of the Jenkins awards
  - Nomination process for Jenkins awards
  - Voting process for Jenkins awards
  - Announcement of Jenkins awards
   - 
   
   Attribution request 
   <https://github.com/jenkins-infra/jenkins.io/issues/6861> for downloads 
   page from JFrog
   - Basil has submitted a draft pull request 
  <https://github.com/jenkins-infra/jenkins.io/pull/6882> for a 
  sponsors page
 - Proposes multiple levels
- Original proposal
   - Anchor
   - Premier
   - Partner
   - Supporter
   - Associate
   - Mirror
- Alternate proposal (Olympic medals + 2 extra)
   - Anchor
   - Gold
   - Silver
   - Bronze
   - Mirror
- Links from the downloads page do not use 
  https://repo.jenkins-ci.org
  - Good to highlight our sponsors (like JFrog) in multiple ways
  - Proposed to list sponsors at the end of the downloads page similar 
  to the end of the root page
 - Include links to a description of the architecture used to 
 distribute Jenkins core and Jenkins plugins
  - 
   
   AWS credits donation reque

Re: 2.440.1 Release Lead

[Mark Waite]

On Friday, January 19, 2024 at 5:00:49 PM UTC-7 Alexander Brandes wrote:

Hey everyone,

As discussed in https://groups.google.com/g/jenkinsci-dev/c/DXf7-uE7gII, I 
am volunteering to be the release lead for 2.440.1.


+1 from me.  Thanks very much!
 

-- 
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/23f40148-13bf-4259-b87a-f3341463ebcbn%40googlegroups.com.

Re: 2.440 as Feb 21, 2024 LTS baseline?

[Mark Waite]

I've added the Jenkins 2.440.1, 2.440.2, and 2.440.3 to the Jenkins events 
calendar 
<https://calendar.google.com/calendar/embed?src=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com>.
  
Dates include:

   - 7 Feb 2024 - 2.440.1 release candidate
   - 21 Feb 2024 - 2.440.1 release
   - 6 Mar 2024 - 2.440.2 release candidate
   - 20 Mar 2024 - 2.440.2 release
   - 3 Apr 2024 - 2.440.3 release candidate and choose next LTS baseline
   - 17 Apr 2024 - 2.440.3 release

Mark Waite

On Tuesday, January 16, 2024 at 1:12:54 PM UTC-7 m...@basilcrow.com wrote:

> +1
>

-- 
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/b6353593-5156-401f-aa59-5c12b4c82266n%40googlegroups.com.

2.440 as Feb 21, 2024 LTS baseline?

[Mark Waite]

Wednesday Jan 10, 2024 is the day that we should select the baseline for 
the long term support release that will be delivered February 21, 2024.

I propose Jenkins 2.440 <https://www.jenkins.io/changelog/#v2.440> as the 
next LTS baseline.  It was released Tuesday Jan 9, 2024.  It includes user 
interface improvements, configuration as code improvements, and 
improvements to the remoting library that communicates with agents.

Feedback is positive on the release.  It is running on weekly.jenkins.io 
and I'm using on my weekly installation.

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/bea3f5b4-bea7-41b4-8344-6bdcb56bc33en%40googlegroups.com.

Re: Partner account credentials for BrowserStack plugin

[Mark Waite]

On Wednesday, January 10, 2024 at 7:16:41 AM UTC-7 Mitesh wrote:

Hi team - I work in the Strategic Partnerships team at BrowserStack. We 
already have an integration with Jenkins and are listed in their plugin 
directory as well. Could you please help me get added as an admin for 
Jenkins' plugin account?


https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ 
describes the process to request to add people as plugin maintainers.

-- 
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/3f9f110d-cfc5-4e48-b469-4c5e1a3dca97n%40googlegroups.com.

Re: January 8, 2024 Governance Board Agenda

[Mark Waite]

On Monday, January 8, 2024 at 12:48:32 PM UTC-7 Gavin wrote:


   - > Kevin Martens retire the Chinese Jenkins site


Is there blockers other than time? its been on the agenda for many many 
many months.


No, just my needing to spend the time to create an environment where I can 
test the changes before proposing pull requests, 

-- 
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/2ddf24e4-c9b7-4c34-989b-256af1e27755n%40googlegroups.com.

January 8, 2024 Governance Board Agenda

[Mark Waite]

Here is the draft agenda

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items


   - Basil create the attribution entries for the downloads page
  - Jenkins sponsors have changed
 - Red Hat is no longer a member of the Continuous Delivery 
 Foundation. Remove from root page <https://www.jenkins.io/>?
 - DigitalOcean donated over $20k USD last year and has donated 
 $20k in 2024
 - AWS donation request has been submitted. Answer in 30 days. If 
 no donation, then should remove AWS from root page 
 <https://www.jenkins.io/>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - Still no progress.
   - Kevin Martens retire the Chinese Jenkins site
   - License policy and phrasing changes
  - What license should be used for a library plugin? (Mailing list 
  thread 
  <https://groups.google.com/g/jenkinsci-dev/c/H7zmC4qHKDc/m/SfL74grPAwAJ>
  )
 - Soft recommendation 
 <https://github.com/jenkins-infra/jenkins.io/pull/6936> has been 
 merged to Jenkins plugin publishing documentation 
 <https://www.jenkins.io/doc/developer/publishing/preparation/#license>
 - If wrapper contains significant code, then use MIT license
 - If wrapper does not contain significant code, then use license 
 of wrapped library
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - 
   
   Artifactory bandwidth reduction project 
   <https://github.com/jenkins-infra/helpdesk/issues/3842> - Mark Waite
   - Results of production deployment
  - Weekend surprises with artifact caching proxy not responding
 - @NotMyFault reported issue-3890 
 <https://github.com/jenkins-infra/helpdesk/issues/3890>
 - @MarkEWaite reported issue-3889 
 <https://github.com/jenkins-infra/helpdesk/issues/3889>
  - Artifact caching proxies were reset earlier today
   - 
   
   Java 11, 17, and 21 in Jenkins - Mark Waite
   - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Mark has much more work to do here
   - Adding a Java version (use Java 21 addition as the pattern)
   - Making a Java version the recommended version (use Java 17 
   as the pattern)
   - Dropping support for a Java version (refer to Java 11 for 
   ideas)
- Further refinements to be done in the JEP
 - Key dates
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
Topics
   
   - 
   
   Defaced issue reports - help desk 3851 
   <https://github.com/jenkins-infra/helpdesk/issues/3851>
   - Jira database restored from backup to Dec 6, 2023 state
 - Changes lost between Dec 6, 2023 and Dec 18, 2023
  - Linux Foundation ticket IT-26276 
  <https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26276> 
opened 
  to request alternatives and their recommendation
 - Jenkins status page 
 <https://status.jenkins.io/issues/2023-12-18-jira-outage/> for Dec 
 18, 2023 restore
  - 
   
   Attribution request 
   <https://github.com/jenkins-infra/jenkins.io/issues/6861> for downloads 
   page from JFrog
   - Basil has submitted a draft pull request 
  <https://github.com/jenkins-infra/jenkins.io/pull/6882> for a 
  sponsors page
 - Proposes multiple levels
- Original proposal
   - Anchor
   - Premier
   - Partner
   - Supporter
   - Associate
   - Mirror
- Alternate proposal (Olympic medals + 2 extra)
   - Anchor
   - Gold
   - Silver
   - Bronze
   - Mirror
- Links from the downloads page do not use 
  https://repo.jenkins-ci.org
  - Good to highlight our sponsors (like JFrog) in multiple ways
  - Proposed to list sponsors at the end of the downloads page similar 
  to the end of the root page
 - Include links to a description of the architecture used to 
 distribute Jenkins core and Jenkins plugins
  - 
   
   Azure credits donation - Damien Duportal
   - Jenkins infrastructure help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3818> is tracking 
  p

Jira upgrade Dec 29, 2023 at 18:00 UTC

[Mark Waite]

The Jira instance at issues.jenkins.io, managed by the Linux Foundation 
team, will be down for up to 30 minutes beginning at 18:00 (UTC) Friday 
December 29, 2023 so that it can be upgraded.

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/91ad33ee-1298-49ea-9d1d-a1ce710ba2d8n%40googlegroups.com.

Re: Jira upgrade Dec 27, 2023 at 18:00 UTC

[Mark Waite]

On Tuesday, December 26, 2023 at 3:33:55 PM UTC-7 Mark Waite wrote:

The Jira instance at issues.jenkins.io, managed by the Linux Foundation 
team, will be down for up to two hours beginning at 18:00 (UTC) Wednesday 
December 27, 2023 so that it can be upgraded.

The status page at https://status.jenkins.io/issues/2023-12-27-jira-upgrade/ 
will be updated when the upgrade is complete.


The maintenance window has closed.  The system update was completed, but 
the Jira upgrade had to be rolled back.  The Linux Foundation 
administrators will investigate and will propose another maintenance window 
when they understand the cause of the Jira upgrade failure.

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/f14c1883-bf64-4d78-8a43-0b2b01e674b5n%40googlegroups.com.

Jira upgrade Dec 27, 2023 at 18:00 UTC

[Mark Waite]

The Jira instance at issues.jenkins.io, managed by the Linux Foundation 
team, will be down for up to two hours beginning at 18:00 (UTC) Wednesday 
December 27, 2023 so that it can be upgraded.

The status page at https://status.jenkins.io/issues/2023-12-27-jira-upgrade/ 
will be updated when the upgrade is complete.

Thanks,
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/8648893c-a95f-4d4f-b6d2-6d001f310a2an%40googlegroups.com.

Re: 2.426.3 Release Lead

[Mark Waite]

On Sunday, December 17, 2023 at 4:55:41 AM UTC-7 Kris Stern wrote:

Hi everyone,

I would be interested in volunteering to be the release lead for LTS 
2.426.3. 


+1 from me.  Thanks for doing it!
 

Best,
Kris Stern


-- 
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/1ac82872-1c25-48f6-9fab-da6d7954108an%40googlegroups.com.

Re: Artifactory configuration change 15 Dec 2023

[Mark Waite]

On Thursday, December 14, 2023 at 8:58:02 AM UTC-7 Mark Waite wrote:

Friday, 15 Dec 2023 at 13:00 UTC, the Jenkins infrastructure team will 
remove the jcenter and oss.sonatype.org-releases repositories from the 
definition of the `*public*` virtual repository 
<https://repo.jenkins-ci.org/artifactory/public/> as part of the effort to 
reduce bandwidth used by repo.jenkins-ci.org.


The change is complete and is working as expected.  Tests that were 
performed to confirm the change include:

   - Build Jenkins core on a freshly created virtual machine
   - Build Jenkins plugin bill of materials weekly line on ci.jenkins.io
   - Build 20+ plugins on a freshly created virtual machine, including the 
   plugins where issues were detected during the brownout
   - Build 250 most popular plugin repositories on an existing machine (a 
   few of them only built successfully when using the pending pull request to 
   test with Java 21)
   - Release a plugin

As far as I can tell, the transition is complete and successful.

Log files contain the expected entries downloading artifacts from Apache 
Maven Central when the artifact is expected to be found there.

Special thanks to Damien Duportal, Basil Crow, Daniel Beck, Bruno 
Verachten, and Jean-Marc Meessen for their help with the changes.

If issues are detected, please open a ticket with the Jenkins infra help 
desk <https://github.com/jenkins-infra/helpdesk/issues> so that we can 
investigate and resolve the issue.

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/5347401e-b0df-4bc0-ae19-525b542cf4e9n%40googlegroups.com.

Artifactory configuration change 15 Dec 2023

[Mark Waite]

Friday, 15 Dec 2023 at 13:00 UTC, the Jenkins infrastructure team will 
remove the jcenter and oss.sonatype.org-releases repositories from the 
definition of the `*public*` virtual repository 
<https://repo.jenkins-ci.org/artifactory/public/> as part of the effort to 
reduce bandwidth used by repo.jenkins-ci.org.

Jenkins plugin developers and Jenkins core maintainers will see a behavior 
change.  Artifacts that are available from Apache Maven Central should be 
downloaded from Apache Maven Central rather than being downloaded from 
https://repo.jenkins-ci.org .  Artifacts that are published to 
https://repo.jenkins-ci.org (like Jenkins war files and Jenkins plugins) 
will continue to be downloaded from https://repo.jenkins-ci.org 

More details are available in help desk ticket 3842 
<https://github.com/jenkins-infra/helpdesk/issues/3842>.

This change will not affect Jenkins controllers or how they receive Jenkins 
plugins.  Jenkins controllers will continue to download plugins from the 
Jenkins update center.

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/1b18f8dd-8df9-476b-875e-fde07eb2bf5cn%40googlegroups.com.

Re: JSON license

[Mark Waite]

Now available as API plugins (thanks to Valentin Delaye!)

   - https://plugins.jenkins.io/gson-api
   - https://plugins.jenkins.io/joda-time-api
   - https://plugins.jenkins.io/json-api
   - https://plugins.jenkins.io/json-path-api

They are included in the plugin bill of materials (2643 
 and 2641 
).  Pull 
requests have been opened to several plugins that were consuming those APIs.
On Thursday, July 27, 2023 at 7:28:33 AM UTC-6 filipe...@premium-minds.com 
wrote:

> If you are obtaining the pom from the hpi, then as you have the hpi why 
> not just see what version if any is in the plugin (WEB-INF/lib/)? 
>
> Did not think of that. It actually seems a better approach. I have added a 
> second sheet with results from this to the spreadsheet. 
>
> Filipe Roque
>

-- 
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/90ef5654-e009-40bd-956c-7bb54c1388a7n%40googlegroups.com.

Re: License for library plugins

[Mark Waite]

On Tuesday, December 12, 2023 at 6:37:18 AM UTC-7 Jesse Glick  wrote:

On Tue, Dec 12, 2023 at 7:44 AM Mark Waite wrote:

The changes made to wrap the library into the plugin are usually not very 
large


Well. In 
https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/blob/d43026ee871292547b224f11d6a2016303720165/src/main/java/io/jenkins/plugins/httpclient/RobustHTTPClient.java#L2-L4
 
for example the code does not consist of “changes” to the wrapped library, 
it is fresh Jenkins-specific development; and while not large it is 
certainly not trivial (well above the threshold considered significant for 
copyright). I think it is appropriate for the *plugin* to remain under the  
MIT license like most of the rest of Jenkins code. Obviously the JAR it 
bundles is under a different license, but so what? The license refers to 
the source files in the repository.

As to plugins which bundle a third-party library and have absolutely 
nothing in `src/` other than `src/main/resources/index.jelly`, I guess it 
is less confusing to just mark the plugin with the same license, though I 
am not sure it makes any practical difference since the only conceivably 
significant “source” would be in `pom.xml` and this is most often pure 
boilerplate plus predictable ``. (Or `cd.yaml`, which is 
almost always just a copy from template.)


I like that very much.  That would keep the Apache HTTP Components 4 
library as MIT licensed but might guide other plugins to adopt the license 
of the library they wrap. 

-- 
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/63509238-bbda-4a33-9467-69b15329419bn%40googlegroups.com.

Re: License for library plugins

[Mark Waite]

On Monday, December 11, 2023 at 12:50:10 PM UTC-7 Basil wrote:

Library plugins are inconsistently licensed: sometimes, they adopt the 
license of the wrapped library, while in other cases, they follow the 
MIT license as normally used by Jenkins plugins. Does anybody have a 
preference as to what we should recommend?


I think that we should recommend that the library plugin should use the 
same license  as the wrapped library.  The changes made to wrap the library 
into the plugin are usually not very large and it feels more consistent to 
me to use the license from the larger body of code that is being wrapped.  
In this case, I'm favoring the license of the wrapped component over the 
MIT license preference of Jenkins core and the Jenkins project.

In order to match that recommendation, I would need to change the license 
of the Apache HttpComponents Client 4.x API plugin 
<https://plugins.jenkins.io/apache-httpcomponents-client-4-api/> from MIT 
to Apache.  A stackoverflow article 
<https://opensource.stackexchange.com/questions/7384/proper-way-of-migrating-mit-licensed-code-to-apache-2-0-license>
 
indicates that the Apache license is a superset of the MIT license, so I 
think it would be enough to change the license text from MIT to Apache, 
without asking each of the contributors if their contribution can be 
assigned the Apache license.  Are there special steps that need to be taken 
when changing a license from MIT to Apache?

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/5aea3749-979e-4d85-b971-8c98ecc0f10fn%40googlegroups.com.

Re: Artifactory brownout Wed 6 Dec 2023 1:00 PM UTC - 3:00 PM UTC

[Mark Waite]

On Monday, December 4, 2023 at 7:22:51 AM UTC-7 Mark Waite wrote:

The Jenkins infrastructure team will remove the jcenter and jcenter-cache 
repositories from the definition of the `*public*` virtual repository 
<https://repo.jenkins-ci.org/artifactory/public/> as part of the effort to 
reduce bandwidth consumption by repo.jenkins-ci.org.

We will perform a two hour "brownout" test Wednesday December 6, 2023 from 
1:00 PM UTC to 3:00 PM UTC.  During that two hour period, the jcenter and 
jcenter-cache repositories will not be included in the public virtual 
repository.  At the end of the two hour brownout, we will insert the 
jcenter and jcenter-cache repositories into the public virtual repository 
again.

During the brownout, we'll perform specific tests as described in help desk 
ticket 3842 <https://github.com/jenkins-infra/helpdesk/issues/3842>.  The 
Jenkins infra team will be performing those tests.  If others would like to 
join the tests, they are welcome to comment in the Jenkins infra chat 
channel <https://matrix.to/#/%23jenkins-infra:matrix.org>.

After the brownout is complete, we'll analyze the results.  If the results 
show no failures, we'll plan to implement the production change next week.  
If the results show failures, we'll resolve the failures and plan for a 
second brownout to confirm that the failures are resolved.


The brownout was a success.  It showed us a few changes that we need to 
make and it confirmed that we're on the right path.

Changes to be made:

   - Add a cache of the Atlassian open source public repository 
   <https://packages.atlassian.com/mvn/maven-atlassian-external> to the 
   public virtual repository so that Jenkins plugins can access the open 
   source Jira integration libraries used in plugins like the Jira plugin.  
   This can be done immediately
   - Remove the jcenter and oss.sonatype.org-releases repositories from the 
   public virtual repository so that Maven Central is used for artifacts 
   provided by Maven Central.  This will be done on Friday

I believe that those are small enough changes that we don't need a second 
brownout to test them.

I propose that we make the production change this Friday at about 2:00 PM 
UTC.  I'll check with the Jenkins infrastructure team tomorrow to confirm 
that Friday works with their schedule.

If the change surprises us with issues,  we'll revert the change and try 
again next week.

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/d050718b-a920-45d4-b3e3-b24ccad6a5a0n%40googlegroups.com.

December 11, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).  
Zoom link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda:

Upcoming Calendar 
   
   - Next LTS: 2.426.2, December 13, 2023
  - Kris Stern is the release lead, backporting pull request 
  <https://github.com/jenkinsci/jenkins/pull/8721> submitted
  - Release candidate delivered Wednesday November 29, 2023
   - Next weekly release: 2.436
   - Two week break in LTS schedule: 2.426.3, January 24, 2024 (6 weeks 
   after 2.426.2 instead of the usual 4 weeks)
  - Refer to developer mailing list discussion 
  <https://groups.google.com/g/jenkinsci-dev/c/vfoiV7HAn94/m/ZHo9h6PSGQAJ> 
for 
  details
  - No break expected in weekly release schedules
   - Next major events:
  - FOSDEM 2024 - February 2-4, 2024
 - Jenkins Contributor Summit Friday February 2, 2024
- Jean-Marc Meessen collecting agenda topics in community forum 

<https://community.jenkins.io/t/jenkins-contributor-summit-on-feb-2-2024-call-for-topics-and-ideas/10689>
 - FOSDEM conference Saturday and Sunday February 3-4, 2024
  
AgendaAction Items
   
   - Basil create the attribution entries for the downloads page
   - Damien create issue to switch agent implementation to virtual machines 
   (*done*)
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023 (*done*)
  - Timeline
 - Blog post 
 <https://www.jenkins.io/blog/2023/12/08/basil-crow-board-announcement/>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site (Kevin Martens)
  - Kevin has started his local Kubernetes development environment to 
  prototype the transition
  - Mark still needs to start his local Kubernetes development 
  environment to prototype the transition
  - Once prototyped, then Kevin and Mark meet with Damien Duportal to 
  review next steps
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
 - Kevin working with the infrastructure team on the Helm charts 
 implementing the Chinese site
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - Basil submitted a governance document pull request 
  <https://github.com/jenkins-infra/jenkins.io/pull/6925> to accept 
  public domain licenses
 - Board approval of the addition of public domain licenses to the 
 governance document
 - Allows the public domain json library and others to be used
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Review responses from other projects to license mixture (e.g. PyPI)
 - Mostly focuses on OSI approved licenses but include a separate 
 category for other licenses
- Have categories for freeware, public domain, and more
- Reasonable precedent for allowing a wider range of licenses
- Needs more discussion, but being more permissive is working 
for PyPI
- Newer licenses may be more controversial
 
Community activity
   
   - 
   
   Jenkins contributor spotlight <https://contributors.jenkins.io/> - Kevin 
   Martens
   - Thanks to Kevin Martens, Kris Stern, Herve Le Meur, Cristina 
  Pizzagalli, and Alyssa Tong
  - Source repository 
  <https://github.com/jenkins-infra/contributor-spotlight/>
  - Upcoming contributors to be highlighted
 - Alex Earl 
 <https://github.com/jenkins-infra/contributor-spotlight/pull/7> - 
 Dec 13, 2023
 - Kris Stern 
 <https://github.com/jenkins-infra/contributor-spotlight/pull/44> - 
 Dec 27, 2023
 - Ulli Hafner 
 <https://github.com/jenkins-infra/contributor-spotlight/pull/50>
  - 
   
   Artifactory bandwidth reduction project - Mark Waite
   - 20 TB of bandwidth used in November, 1/3 due to cached artifacts from 
  Apache Maven Central
 - JFrog has asked that we remove the cached artifacts from the 
 Jenkins public virtual repository
  - Artifactory brownout 
  <https://groups.google.com/g/jenkinsci-dev/c/Jn_4U-KQUqg/m/N5i6VH7_AAAJ> 
last 
  Wednesday 6 Dec 2023
 - Jenkins core build passed during brownout
 - Repository permissions updater build failed during brownout due 
  

Re: bitbucket-plugin - why didn't my PR got released

[Mark Waite]

On Sunday, December 10, 2023 at 10:04:17 AM UTC-7 Tzach wrote:

Thanks Mark as always :) 

Is there a way to "fix" the current PR or should I create a new one? 


Apply the label to the existing pull request and then run the cd action 
from the "Actions" menu of the repository.

That's worked for me in the past.

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/9a455bf0-5e5d-480e-a99c-14ea8b4eb96dn%40googlegroups.com.

Re: bitbucket-plugin - why didn't my PR got released

[Mark Waite]

The change detector inside the continuous delivery step is checking the 
labels on the pull request.  That pull request is not labeled.  It has 
"BREAKING CHANGE" in the title, but does not have a label.

I think that you want the label "developer" rather than "breaking", since 
changing the minimum required Jenkins version is not considered to be a 
breaking change.

On Sunday, December 10, 2023 at 8:34:01 AM UTC-7 tzach@gmail.com wrote:

> Hi all,
>
> I've labeled my PR-97 
>  with "BREAKING 
> CHANGE:" but it was not released.
> What am I missing?
>
> Thanks,
> Tzach
>
>

-- 
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/46e078a2-0dcd-4903-8651-8702c5257128n%40googlegroups.com.

Artifactory brownout Wed 6 Dec 2023 1:00 PM UTC - 3:00 PM UTC

[Mark Waite]

The Jenkins infrastructure team will remove the jcenter and jcenter-cache 
repositories from the definition of the `*public*` virtual repository 
<https://repo.jenkins-ci.org/artifactory/public/> as part of the effort to 
reduce bandwidth consumption by repo.jenkins-ci.org.

We will perform a two hour "brownout" test Wednesday December 6, 2023 from 
1:00 PM UTC to 3:00 PM UTC.  During that two hour period, the jcenter and 
jcenter-cache repositories will not be included in the public virtual 
repository.  At the end of the two hour brownout, we will insert the 
jcenter and jcenter-cache repositories into the public virtual repository 
again.

During the brownout, we'll perform specific tests as described in help desk 
ticket 3842 <https://github.com/jenkins-infra/helpdesk/issues/3842>.  The 
Jenkins infra team will be performing those tests.  If others would like to 
join the tests, they are welcome to comment in the Jenkins infra chat 
channel <https://matrix.to/#/%23jenkins-infra:matrix.org>.

After the brownout is complete, we'll analyze the results.  If the results 
show no failures, we'll plan to implement the production change next week.  
If the results show failures, we'll resolve the failures and plan for a 
second brownout to confirm that the failures are resolved.

More details may be discussed tomorrow at 2:30 PM UTC in the weekly Jenkins 
infra team meeting.  See the Jenkins events calendar 
<https://www.jenkins.io/events/> for the link to the weekly Jenkins infra 
team meeting.

Thanks,
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/2d00fcab-bb00-40f7-b4eb-3ca68fd2e248n%40googlegroups.com.

Re: jenkins-2.426.2-rc-1 has been released

[Mark Waite]

I've installed it in my environment and have found no issues.  I'll 
continue using it as my test configuration.

On Thursday, November 30, 2023 at 6:53:18 AM UTC-7 Kris Stern wrote:

Other info relevant for the LTS 2.426.2 RC:

Please report issues found to this release candidate announcement thread.

Final release is scheduled for 2023-12-13.

-- 
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/9d5878bc-538b-4671-a42b-a484e03de83cn%40googlegroups.com.

issues.jenkins.io upgrade 7 Dec 2023 at 10:00 PM UTC

[Mark Waite]

The Jenkins JIRA instance will be down for up to 30 minutes beginning at 
10:00 PM UTC on Thursday, December 7, 2023.

Special thanks to the Linux Foundation for hosting our JIRA instance and 
assuring that it is current and well maintained.

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/54ada4cd-b2c7-4397-b40f-a5aa81929954n%40googlegroups.com.

Re: Hosting New Jenkins plugin on Jenkins

[Mark Waite]

https://updates.jenkins.io/latest/amazon-inspector-image-scanner.hpi?mirrorlist 
shows that the plugin is already available on 4 of the mirrors.

https://plugins.jenkins.io/amazon-inspector-image-scanner/ shows it is 
available on the plugins site (at least to me).

Mark Waite

On Thursday, November 30, 2023 at 12:31:02 PM UTC-7 ga...@gavinmogan.com 
wrote:

> we usually say up to 3 hours since multiple parts have to line up, but 
> could be up to 6 if you miss a window.
>
>
> https://github.com/jenkins-infra/plugin-site/blob/master/Jenkinsfile_k8s#L57 
> runs every 3hours
> It uses data from update center (which I can't find the config for, but 
> run every 5 or 15 min i forgot)
>
> On Thu, Nov 30, 2023 at 11:23 AM Adrien Lecharpentier <
> adrien.lec...@gmail.com> wrote:
>
>> I don't recall exactly but someone in the community might know exactly 
>>
>> Le jeu. 30 nov. 2023, 18:59, naveen sharma  a écrit :
>>
>>> Hi Adrien, Please suggest What's the frequency to update The plugin site 
>>> (plugins.jenkins.io). We are announcing it shortly and expecting to be 
>>> available on plugins.jenkins.io.
>>>
>>> On Thu, Nov 30, 2023 at 11:52 AM naveen sharma  
>>> wrote:
>>>
>>>> Got it. I will work with Will to delete original repo this, once we 
>>>> validate plugin on marketplace.
>>>>
>>>> The plugin site (plugins.jenkins.io) will be updated soon. -- Within 1 
>>>> hr? or less
>>>>
>>>>
>>>> On Thu, Nov 30, 2023 at 11:43 AM Adrien Lecharpentier <
>>>> adrien.lec...@gmail.com> wrote:
>>>>
>>>>> So, there is a release. 
>>>>> The release is available in the update center (
>>>>> https://updates.jenkins.io/current/update-center.json)
>>>>>
>>>>> The plugin site (plugins.jenkins.io) will be updated soon. 
>>>>>
>>>>> One thing, for the hosting process, we request that the original 
>>>>> repository of the plugin be deleted so that the one in jenkinsci 
>>>>> organization is not seen as a fork.
>>>>>
>>>>>
>>>>>
>>>>> Le jeu. 30 nov. 2023, 17:32, naveen sharma  a 
>>>>> écrit :
>>>>>
>>>>>> Hi Adrien,
>>>>>>
>>>>>> Quick help
>>>>>>
>>>>>> We have this final PR 
>>>>>> https://github.com/jenkinsci/amazon-inspector-image-scanner-plugin/pull/3#issuecomment-1834108500
>>>>>>
>>>>>> Please suggest by when we can see our plugin to marketplace.
>>>>>>
>>>>>> Regards,
>>>>>> Naveen 
>>>>>>
>>>>>> On Wed, Nov 29, 2023 at 6:28 PM naveen sharma  
>>>>>> wrote:
>>>>>>
>>>>>>> Thank you for your help!
>>>>>>>
>>>>>>> On Wed, Nov 29, 2023 at 5:34 PM Adrien Lecharpentier <
>>>>>>> adrien.lec...@gmail.com> wrote:
>>>>>>>
>>>>>>>> I saw that you tried to enable CD on the repository but the action 
>>>>>>>> description is not located in the correct directory. 
>>>>>>>>
>>>>>>>> The file must be in `.github/workflows`.
>>>>>>>>
>>>>>>>> Then you will need to label a pull request with the label 
>>>>>>>> `developer` for example. (Use the one you'll use to fix the cd action 
>>>>>>>> file). Once the pull request is merged, you should see a new release.
>>>>>>>>
>>>>>>>> Le mer. 29 nov. 2023, 23:16, Adrien Lecharpentier <
>>>>>>>> adrien.lec...@gmail.com> a écrit :
>>>>>>>>
>>>>>>>>> Yes you need. 
>>>>>>>>> Everything is detailed here 
>>>>>>>>> https://www.jenkins.io/doc/developer/publishing/releasing/
>>>>>>>>>
>>>>>>>>> Le mer. 29 nov. 2023, 21:40, naveen sharma  a 
>>>>>>>>> écrit :
>>>>>>>>>
>>>>>>>>>> Hi Adrien, do we need permission for publishing plugin ?
>>>>>>>>>>
>>>>>>>>>> Can you suggest process please 
>>>>>>>>>>
>>>>>>>>>> O

November 27, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 30 minutes from 
now).  Zoom link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda:

News
   
   - Jenkins 2.426.1 released Nov 15, 2023
  - Ratings <https://www.jenkins.io/changelog-stable/#v2.426.1> look 
  very good
 - 79 reports of “no major issues”
 - 1 report of “I experienced notable issues”, but without an issue 
 number
 - 0 reports of “I had to roll back”
  - Prototype.js removed
  - Java 11 end of life administrative monitor shown to users running 
  Java 11
  - No support for Red Hat Enterprise Linux 7 and derivatives
  - Java 21 supported
 - One Java 21 intermittent memory leak 
 <https://issues.jenkins.io/browse/JENKINS-72325> as reported by 
 automated tests
- Script security plugin pull request 
<https://github.com/jenkinsci/script-security-plugin/pull/543> 
merged 
to resolve the memory leak
- Script security plugin release 1294.v99333c047434 

<https://github.com/jenkinsci/script-security-plugin/releases/tag/1294.v99333c047434>
 - Jira issues being watched closely
 - One issue about adjunct removed that needs more investigation
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Mark create issue to drop the weekly build of BOM in favor of human 
   launched build (done)
   - Basil create issue to drop middle two lines from BOM full-test label
   - Damien create issue to switch agent implementation to virtual machines
   - Ulli propose a PR revising the election process to
  - nominate 1 month earlier
  - only register voters if more than one person is a candidate for at 
  least one position
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - Timeline
 - Results announcement (December 11)
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site (Kevin Martens)
  - Kevin has started his local Kubernetes development environment to 
  prototype the transition
  - Mark still needs to start his local Kubernetes development 
  environment to prototype the transition
  - Once prototyped, then Kevin and Mark meet with Damien Duportal to 
  review next steps
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
 - Kevin working with the infrastructure team on the Helm charts 
 implementing the Chinese site
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - No further progress
  - Allow other licenses like the JSON license
  - Some other approach?
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Review responses from other projects to license mixture (e.g. PyPI)
 - Mostly focuses on OSI approved licenses but include a separate 
 category for other licenses
- Have categories for freeware, public domain, and more
- Reasonable precedent for allowing a wider range of licenses
- Needs more discussion, but being more permissive is working 
for PyPI
- Newer licenses may be more controversial
 - Mark Waite update the governance meeting GitHub repository with 
   the latest meeting notes
  - No progress
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Mark has much more work to do here
   - Adding a Java version (use Java 21 addition as the pattern)
   - Making a Java version the recommended version (use Java 17 
   as the pattern)
   - Dropping support for a Java version (refer to Java 11 for 
   ideas)
- Further refinements to be done in the JEP
 - Key dates
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 supp

Re: How can I test my plugin in pipeline?

[Mark Waite]

The Hello World example assumes that the declarative Pipeline is 
installed.  If it is not installed, then you'll need to install it.

On Thursday, November 16, 2023 at 7:58:09 AM UTC-7 tzach@gmail.com 
wrote:

> Hi,
>
> I'm following the tutorial of creating a new plugin and I want to test it 
> in pipeline but beforehand I just wanted to check that pipeline job is 
> working OK, so I've created a new pipeline using the Hello World template 
> of pipeline script but it does not work OK.
> What I'm seeing is this:
>
> Started by user unknown or anonymous[Pipeline] Start of Pipeline 
> [Pipeline] End of 
> PipelineFinished: SUCCESS
>
>
> What am I missing?
>
> Thanks,
> Tzach
>

-- 
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/36d5e6e9-ede4-490f-9500-15da22e2f472n%40googlegroups.com.

Re: Jenkins 2.426.2 release lead

[Mark Waite]

On Wednesday, November 15, 2023 at 1:38:07 PM UTC-Kris Stern wrote:

Hi Mark,

I am interested.

Best,
Kris


That is super Kris.  Thanks for doing it. 

-- 
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/9683adc7-ba22-41bb-89cd-c51db55ae037n%40googlegroups.com.

Jenkins 2.426.2 release lead

[Mark Waite]

Hello,

We need a volunteer to act as the release lead for Jenkins 2.426.2.

Planned dates are visible on the event 
caelndar: https://www.jenkins.io/events/#event-calendar 


   - Release candidate 29 Nov 2023 (two weeks from today)
   - Release 13 Dec 2023

The documentation is available 
at 
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
  
 Previous release checklists can be very helpful as well, since they tend 
to include comments and notes from the release lead.

Previous release leads will be available to answer questions and provide 
guidance.

I started a prototype of the backporting pull request 
at  https://github.com/jenkinsci/jenkins/pull/8681

We chat in #jenkins-release on libera IRC, 
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix 
channel.

Thanks,
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/e323f659-1110-4286-a64b-2adfb3f5759cn%40googlegroups.com.

Re: Intelligent test report

[Mark Waite]

Thanks so much for the offer!  I'd love to see the pull request proposing 
the addition.

We discussed it in board meeting earlier this week and all those in 
attendance at the meeting agreed that this is a good thing to explore 
further.

Looking forward to the pull request(s).

Mark Waite

On Friday, November 10, 2023 at 11:14:38 AM UTC-7 Kohsuke Kawaguchi wrote:

> Hi, fellow Jenkins folks,
>
> I'm here with what I hope to be a win-win offer, which might sound shady 
> :-), but hear me out!
>
> At Launchable, we are trying to use data from tests to make devs more 
> productive. As a part of that effort, we are actively building what I call 
> "intelligent test session report". The easiest way to think of it is the 
> equivalent of the test report page like this 
> <https://ci.jenkins.io/job/Core/job/jenkins/job/master/lastUnstableBuild/testReport/>,
>  
> except it's more intelligent:
>
>- When one issue breaks multiple tests, they get grouped together (by 
>LLM)
>- Failures get summarized by LLM to help you quickly get to the most 
>important failure
>- Historical information -- new vs ongoing failures
>- Failures annotated by attributes of tests, such as "flaky test", 
>"never failing test", etc.
>
> Admittedly, this is still an early product, as there are tons we can/want 
> to do, but I believe it's already usable, and I'm looking for people who 
> are willing to kick tires, and give us suggestions & feedback to improve 
> them. So I naturally thought of the Jenkins project, where I know we have 
> no shortage of devs who have opinions about tools they use!
>
> Would it be OK if I submit the necessary change in the CI pipeline & 
> others to get this feature activated for Jenkins core? This is of 
> course free.
>
> Just to give you some idea of what this would look like, here's one test 
> report. 56 tests failed in this run, but we were able to group them into 3 
> distinct issues, and the summary makes it clear that two of them are some 
> Spring issues, and the last one is sendgrid (library?) versioning problem.
>
> [image: image.png]
> -- 
> Kohsuke Kawaguchi
>

-- 
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/3d594c03-1348-4c6e-adf3-f04e44f196can%40googlegroups.com.

November 13, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 40 minutes from 
now).  Zoom link 
is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda

News

   - Alex Brandes receives GitHub Supply Chain Sentinel award 
   
<https://github.blog/2023-11-09-celebrating-the-github-awards-2023-recipients/#supply-chain-sentinel-award>
  - Jenkins Twitter 
  <https://x.com/jenkinsci/status/1723024441649561635?s=20>
  - Jenkins LinkedIn 
  <https://www.linkedin.com/feed/update/urn:li:activity:7128787406882832384>
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - 57 registered voters
  - Timeline
 - Nominations are closed (September 18 - October 27)
- All roles have at least one nominee
   - If role is uncontested, then no need to vote
- If candidates agree to accept the nomination and they are 
only nominee, then they are elected
 - Voter registration is closed (September 18 - November 05)
 - Voting (November 06 - December 1)
 - Results announcement (December 11)
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site (Kevin Martens)
  - Chinese site link removed from www.jenkins.io header
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
 - Kevin working with the infrastructure team on the Helm charts 
 implementing the Chinese site
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - No further progress
  - Allow other licenses like the JSON license
  - Some other approach?
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Review responses from other projects to license mixture (e.g. PyPI)
 - Mostly focuses on OSI approved licenses but include a separate 
 category for other licenses
- Have categories for freeware, public domain, and more
- Reasonable precedent for allowing a wider range of licenses
- Needs more discussion, but being more permissive is working 
for PyPI
- Newer licenses may be more controversial
 - Mark Waite update the governance meeting GitHub repository with 
   the latest meeting notes

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - 
   
   Intelligent test report experiment from Kohsuke Kawaguchi
   - Developer mailing list request 
  <https://groups.google.com/g/jenkinsci-dev/c/kyqiprKYc68/m/P6ZpxWpLAgAJ> 
seeking 
  users to explore it
 - Kohsuke asks, “Would it be OK if I submit the necessary change 
 in the CI pipeline & others to get this feature activated for Jenkins 
core?”
      - 
   
   Java 11, 17, and 21 in Jenkins - Mark Waite
   - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Currently gathered in a block comment in Jenkins core
- Making a Java version the recommended version
- Dropping support for a Java version
- Allow future release leads and other contributors to use the 
document
- Further refinements to be done in the JEP
 - Summary of discussions
 - Jenkins developers mailing list 
 
<https://groups.google.com/g/jenkinsci-dev/c/RaAloTTM9CQ/m/kag1KJSVAwAJ> - 
 quiet
 - Jenkins users mailing list 
 
<https://groups.google.com/g/jenkinsci-users/c/NGDRrNsaDYY/m/zj5RpSNSAQAJ> - 
 quiet
 - Jenkins enhancement proposal 
 
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11> - 
 in progress
  - Key dates
 - Oct 3, 2023 - Java 11 end of life monitor visible in Jenkins 
 weekly
 - Nov 15, 2023 - Java 11 end of life monitor visible in Jenkins LTS
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  - 
   
   Hacktoberfest c

Re: Backporting for 2.426.1 has started

[Mark Waite]

The second LTS release candidate for Jenkins 2.426.1 has been published and 
is ready to be tested.

Final release is scheduled for 2023-11-15.

Download the release candidate from Artifactory 
<https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.426.1-rc34276.4c564b_0ed81d/jenkins-war-2.426.1-rc34276.4c564b_0ed81d.war>
.

Mark Waite
On Thursday, November 9, 2023 at 1:57:15 PM UTC-7 Mark Waite wrote:

> A new 2.426.1 release candidate should be available within the next 24 
> hours.  When it is available, it would be great to have additional 
> testing.  A link to the war file will be included in this thread.
>
> The new release candidate has updated the version of the SnakeYAML API 
> plugin bundled in Jenkins 2.426.1.  Jenkins 2.426 bundles SnakeYAML API 
> plugin 1.33-x.  Jenkins 2.426.1 will bundle SnakeYAML API plugin 2.2-x.  
> The update will reduce the number of (inaccurate) complaints from security 
> scanners.
>
> 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/683a0694-5f8d-4c3f-8d32-c676838347e9n%40googlegroups.com.

Re: Backporting for 2.426.1 has started

[Mark Waite]

A new 2.426.1 release candidate should be available within the next 24 
hours.  When it is available, it would be great to have additional 
testing.  A link to the war file will be included in this thread.

The new release candidate has updated the version of the SnakeYAML API 
plugin bundled in Jenkins 2.426.1.  Jenkins 2.426 bundles SnakeYAML API 
plugin 1.33-x.  Jenkins 2.426.1 will bundle SnakeYAML API plugin 2.2-x.  
The update will reduce the number of (inaccurate) complaints from security 
scanners.

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/c15bb30c-466c-40d0-a75d-88846851e5e8n%40googlegroups.com.

Re: October 30, 2023 Governance Board Agenda

[Mark Waite]

On Mon, Oct 30, 2023 at 1:37 PM Ullrich Hafner wrote:

> Hmm, it seems that I missed the meeting. It was not adapted to the winter
> time, sorry. Can we move it again back to the same local time?
>
>
Meeting time has been adjusted to start at 6:00 PM Berlin time.  I should
have switched from UTC time for that meeting long ago, since we need the
meeting time to adjust to the transitions between winter time and summer
time in Germany.

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

October 30, 2023 Governance Board Agenda

[Mark Waite]

News
   
   - Jenkins elections 2023 nominations have closed - Alexander Brandes and 
   Ulli Hafner

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - 57 registered voters
  - Timeline
 - Nominations are closed (September 18 - October 27)
- All roles have at least one nominee
   - If role is uncontested, then no need to vote
- If candidates agree to accept the nomination and they are 
only nominee, then they are elected
 - Voter registration (September 18 - November 05)
 - Voting (November 06 - December 1)
 - Results announcement (December 11)
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site - deadline for 4 weeks to close (Kevin 
   Martens)
  - Chinese site link removed from www.jenkins.io header
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
 - Need a redirect from https://www.jenkins.io/zh/ to 
 https://www.jenkins.io/ <https://www.jenkins.io/zh/>
 - Kevin to work with the infrastructure team on the Helm charts 
 implementing the Chinese site
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - Discussed briefly at Linux Foundation Member Summit
 - Linux Foundation legal team is willing to review proposal
  - No further progress
  - Allow other licenses like the JSON license
  - Some other approach?
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Review responses from other projects to license mixture (e.g. PyPI)
 - Mostly focuses on OSI approved licenses but include a separate 
 category for other licenses
- Have categories for freeware, public domain, and more
- Reasonable precedent for allowing a wider range of licenses
- Needs more discussion, but being more permissive is working 
for PyPI
- Newer licenses may be more controversial
 
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - 2+2+2 Java support plan - Jenkins enhancement proposal 
  
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
   submitted
 - Ready to assign a JEP number and mark as a Draft
 - Mark Waite to assign the JEP and mark as a Draft
  - Summary of discussions
 - Jenkins developers mailing list 
 
<https://groups.google.com/g/jenkinsci-dev/c/RaAloTTM9CQ/m/kag1KJSVAwAJ> - 
 quiet
 - Jenkins users mailing list 
 
<https://groups.google.com/g/jenkinsci-users/c/NGDRrNsaDYY/m/zj5RpSNSAQAJ> - 
 quiet
 - Jenkins enhancement proposal 
 
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11> - 
 needs review
  - Key dates
 - Oct 3, 2023 - Java 11 end of life monitor visible in Jenkins 
 weekly
 - Nov 15, 2023 - Java 11 end of life monitor visible in Jenkins LTS
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  - Hacktoberfest nearing its end
  - Jean-Marc Meessen message to developer list 
  <https://groups.google.com/g/jenkinsci-dev/c/wwtLLHNYAjo/m/ZcnRpsRUAAAJ>
  - Friendly Jira issues list 
  <https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=19342>
  - GitHub good first issues 
  
<https://github.com/search?q=org%3Ajenkinsci+good-first-issues=issues>
  - Infrastructure good first issues 
  
<https://github.com/search?q=org%3Ajenkins-infra+good-first-issues=issues>
  - Gitter requests that look for “where to start?”
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
Topics
   
   - 
   
   Board and officer elections - Alexander Brandes *
   - 
   
   Processing the Azure credits donation - Mark Waite
   - Damien Duportal outlined alternatives in email message to the board
   - 
   
   Donation of Oracle Cloud costs by CloudBees - Mark Waite
   - Oracle Cloud account remains open until Oracle agrees all invoices are 
  res

Backporting for 2.426.1 has started

[Mark Waite]

Backporting for 2.426.1 has started, and the RC is scheduled for 2023-11-01.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.426.1-fixed
Rejected: 
https://issues.jenkins.io/issues/?jql=labels%20%3D%202.426.1-rejected

If there are other issues that you would like to see backported to 2.426.1, 
please add teh lts-candidate label to the issue so that it can be reviewed.

The stable-2.426 branch is available and passing tests on ci.jenkins.io

Best regards,

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/e277ecfe-aad8-4003-a669-28f420029941n%40googlegroups.com.

Re: Plug-in adoption

[Mark Waite]

Not much. I am a manager that was a C programmer many years ago.  I have
learned Java and Maven as part of Jenkins plugin maintenance and a little
experience before Jenkins.

If you are interested in learning and are willing to learn, you can adopt a
plugin.

Technical questions to the developer list frequently get good answers.  If
you'd like others to review your changes,  I am sure we can find people
willing to answer questions and review changes

On Thu, Oct 26, 2023, 1:11 PM STEVEN CORREA  wrote:

> Hello everyone -
>
> What is the minimum level of development experience needed to adopt a
> plug-in?
>
> Regards,
> Steve
>
> --
> 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/566a1ed2-1118-412c-a67d-d568aaf6df4en%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/CAO49JtHpD5RomKdNUJ6SJ9WOwBAX6SXBRjzboCgzrxizn2SLPQ%40mail.gmail.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

On Thursday, October 26, 2023 at 9:29:00 AM UTC-6 Jiri Vanek wrote:

I see. That sounds like correct assumption. Only JDK will become LTS only 
and if only somebody pick it up. So yes, the statement is correct - We can 
be pretty sure that once per 2 years, at last one JDK indeed will be picked 
by any of 
bigger java players. And if so, it is most likely being aligned with 
oracle. 

Thanx for those additional details and sorry for noise. 


Thanks to you as well for being involved and for sharing your concern.
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/f70987ed-29b2-4289-96e6-dfb254d9f5d5n%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

On Thursday, October 26, 2023 at 8:12:02 AM UTC-6 Jiri Vanek wrote:

Maybe a small narrowing. 
The LTS every two years means that Oracle java will be following that. And 
that is beyond paywall. 
The usptream openjdk is simply rolling with new jdk every half a year, and 
of it nothing is going to be LTS, unless somone to pick that particular 
repository and keep maintain that, and keep building that (here, eclisdpe 
adoptium will be 
most likely building ever jdk repo which have maintainer). See eg AZUL 
maintaing LTS of JDK13 and few others...


Thanks for the comment Jiri.  Much appreciated.

I'm relying on the statement on the Eclipse Temurin Release Roadmap 
<https://adoptium.net/support/#_release_roadmap> where it says

> In addition, every two years since 2021 one feature release will be 
designated as a Long Term Supported (LTS) release. We will support LTS 
releases for at least four years.

Since Eclipse Temurin will support an LTS JDK for at least four years after 
its initial release, I think that the Jenkins project can rely on that.

Mark Waite
 

-- 
Jiri Vanek Mgr. 
Principal QA Software Engineer 
Red Hat Inc. 
+420 775 39 01 09 

-- 
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/24879b7a-e2a3-4c32-87c7-62f8e838c3c8n%40googlegroups.com.

Re: Can an admin restart a build ?

[Mark Waite]

Done.  Thanks for the pull request.

On Monday, October 23, 2023 at 9:30:30 PM UTC-6 jone...@gmail.com wrote:

> Hi,
>
> Is it possible that a https://ci.jenkins.io/ admin restart the following 
> build ? https://github.com/jenkinsci/mstest-plugin/pull/24 (
> https://ci.jenkins.io/job/Plugins/job/mstest-plugin/view/change-requests/job/PR-24/
> )
>
> Based on my previous contributions, there is low chance a PR get reviewed 
> by maintainer when failing due to changes on Jenkinsfile
>
> Thanks!
>

-- 
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/49654645-7e42-404b-b7d7-49c601ac8bd5n%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

Two diagrams have been added to the Jenkins Enhancement Proposal 
<https://github.com/jenkinsci/jep/blob/cd176912ed8797ddee1066be59b1a68fb9b6bc77/jep//README.adoc>.
  
One diagram shows a single Java version (Java 25) to highlight the 
lifecycle of a single Java version in the Jenkins community.  The other 
diagram shows the transition across multiple Java versions.  The pull 
request <https://github.com/jenkinsci/jep/pull/400> includes the 
discussions.

The duration of the alert period that precedes the transition from one 
minimum Java version to the next minimum Java version is still being 
discussed.  The current implementation in Jenkins core provides begins 
notifying 18 months before the change and then notifies again 9 months 
before the change.  James Nord feels that it would be better to notify 12 
months before the change and refresh 6 months before the change.  The pull 
request conversation 
<https://github.com/jenkinsci/jep/pull/400#discussion_r1360372868> has the 
details.

Tim Jacomb (a JEP editor) has agreed that the proposal is ready to be 
assigned a JEP number and to enter "Draft" state.  I'll plan to do that 
within the next few days.

Assigning a JEP number does not prevent us from correcting or improving the 
JEP.  Changes, corrections, and improvements are allowed to draft JEPs.

Mark Waite
On Saturday, October 14, 2023 at 5:21:54 AM UTC-6 Mark Waite wrote:

> I've created a Jenkins Enhancement Proposal based on this draft.  Comments 
> are welcomed at https://github.com/jenkinsci/jep/pull/400
>
> On Monday, September 25, 2023 at 7:18:40 AM UTC-6 Mark Waite wrote:
>
>> Java releases are delivered every 6 months with a long term support 
>> release every two years as announced in a September 2021 blog post 
>> <https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.
>>   
>> The release cadence is described in more detail in another blog post 
>> <https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
>> The OpenJDK project and Eclipse Temurin project both support their long 
>> term support releases with security patches for six years.
>>
>> The two year release cadence with a six year support life means that 
>> three Java LTS releases are officially supported at any point in time by 
>> the OpenJDK project and the Eclipse Temurin project.  Jenkins developers 
>> would like to generally support two Java LTS releases rather than three LTS 
>> releases in order to reduce overhead from supporting Java releases.
>>
>> In order to limit Java support to two LTS releases, I propose that the 
>> Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
>> supported for two years, then becomes the minimum required Java version for 
>> two years, then is unsupported for two years.  In the last two years, new 
>> Jenkins releases will not run on that oldest supported Java version.
>>
>> A diagram 
>> <https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
>>  
>> is provided to describe the transition from our current model to the 
>> “2+2+2” model.
>>
>> The diagram shows that as part of the transition, Java 17 will be the 
>> minimum required Java version for only 12 months and Java 21 will be the 
>> minimum required version for only 18 months.  Java 25 and later will be the 
>> minimum required version for 24 months.
>>
>> The “2+2+2” pattern balances the needs of large scale Jenkins users for 
>> predictability and stability and the needs of Jenkins developers for less 
>> maintenance overhead.
>>
>> After a week or two of discussion in the Jenkins developer mailing list 
>> and the Jenkins user mailing list, I plan to submit this as a Jenkins 
>> Enhancement Proposal.
>>
>> More details are available in the Google Doc 
>> <https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
>> .
>>
>> Thanks,
>> 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/4c324d9b-c5a2-483a-9a10-355140639878n%40googlegroups.com.

Mark Waite as release lead for 2.426.1?

[Mark Waite]

It has been quite a while since I last acted as a release lead for a 
Jenkins LTS release.  I'd like to be the release lead for Jenkins 2.426.1.  
Jenkins 2.426.1 is scheduled to release Nov 15, 2023.

I've been testing 2.426 in my development environment and am interested in 
several of its changes.  Some of those changes include:

   - Removal of Prototype.js JavaScript library
   - Addition of the Java 11 end of life Administrative Monitor
   - End of life for Red Hat Enterprise Linux 7 and its derivatives


I'll need coaching and reviews from Kris Stern, Alexander Brandes, and Tim 
Jacomb.

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/e739cb3f-dffc-4661-a498-7d85d791ec22n%40googlegroups.com.

Re: Adoption request extra-tool-installers-plugin

[Mark Waite]

+1 from me.  Thanks for being willing to adopt the plugin.

On Friday, October 20, 2023 at 11:33:45 PM UTC-6 jone...@gmail.com wrote:

> Hi,
>
> This is an adoption request for extra-tool-installers-plugin that is for 
> adoption 
>
> I would like to it refreshed, add test for JCasC and more test coverage
>
> Planning to use it in real life specially for the retry installer
>
>
>- 
>
>Link to a plugin you want to adopt 
>https://github.com/jenkinsci/extra-tool-installers-plugin
>- 
>
>The status of the plugin: abandoned
>- 
>
>Link(s) to pull requests you want to deliver, if applicable: Not yet
>- 
>
>Your GitHub username/id : jonesbusy
>- 
>
>Your Jenkins infrastructure account id: jonesbusy
>- 
>
>The link to the "Repository Permission Updater" PR described below: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3577
>
> Regards,
>

-- 
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/84a7bc0d-3bba-4688-bf7f-597fdf60ebe1n%40googlegroups.com.

Re: Backporting for LTS 2.414.3 has started

[Mark Waite]

On Wednesday, October 18, 2023 at 2:09:37 AM UTC-6 Alexander Brandes wrote:

Packaging happens from the versioned stable-2.414 branch.

There's a stable- branch for every recent LTS release.


You're right.  I'm not sure how I made the mistake of not seeing that 
branch, but I clearly did not see it in the session where Kevin and I were 
investigating.  

Unfortunately, I'm not available to create the cherry pick commit because I 
need to leave for the airport.

I'm +1 for the cherry-pick, but also have no problem if the curl based 
instructions remain so that we don't disrupt today's release.

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/e6e77e1d-2229-4412-87f0-0a6534aa9142n%40googlegroups.com.

Re: Backporting for LTS 2.414.3 has started

[Mark Waite]

On Monday, October 16, 2023 at 7:05:03 PM UTC-6 Mark Waite wrote:

On Friday, October 13, 2023 at 9:42:27 AM UTC-6 Alexander Brandes wrote:

I would like to propose backporting a documentation change [0], ensuring 
the installation pages match the instructions on jenkins.io.


I am "+1" for the documentation backport.


Kevin and I investigated and as far as we can tell, a backport is not 
needed because the master branch is used for packaging.  There are no 
recent stable-xxx branches in the packaging repository.

When the build runs tomorrow, the LTS documentation for Debian on 
https://pkg.jenkins.io/debian-stable/ will be updated to match the weekly 
documentation.

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/d396-6c64-4e96-904c-c7656f580a01n%40googlegroups.com.

Re: Backporting for LTS 2.414.3 has started

[Mark Waite]

On Friday, October 13, 2023 at 9:42:27 AM UTC-6 Alexander Brandes wrote:

I would like to propose backporting a documentation change [0], ensuring 
the installation pages match the instructions on jenkins.io.


I am "+1" for the documentation backport.
 

Additionally, a remoting PR has been labeled as “backporting-candidate”.

[0] https://github.com/jenkinsci/packaging/pull/435
[1] https://github.com/jenkinsci/remoting/pull/675


I think that the remoting backport should wait 2.426.1 and be backported 
there.  It hasn't reached a weekly release yet.

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/cb51d40c-093a-4b9b-a9ed-e8f0c9fea364n%40googlegroups.com.

October 16, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts in about one hour 
at https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Proposed agenda items are listed below:

News
 Comment

   - Jenkins elections 2023 nominations in progress - Alexander Brandes and 
   Ulli Hafner
  - Announced by blog post 
  
<https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/>
  , community post 
  
<https://community.jenkins.io/t/jenkins-board-and-officer-election-2023/9644>
  , tweet <https://twitter.com/jenkinsci/status/1703772922593132972>, 
  LinkedIn 
  
<https://www.linkedin.com/feed/update/urn:li:activity:7109540080251244546>, 
  and jenkins-infra <https://github.com/jenkins-infra>
  - Need more nominees
  - Need more registered voters (currently 50 registered)
   - Cloudflare sponsors Jenkins project
  - Project to host update center content on Cloudflare R2 buckets 
  worldwide
 - Reduce AWS costs for the Jenkins project
  - Java 21 released <https://openjdk.org/projects/jdk/21/> September 
   19, 2023
  - Java 21 testing
 - Jenkins core, acceptance test harness, and plugin bill of 
 materials successful with Java 21
 - Over 100 plugins testing successfully with Java 21
  - Summary blog post with Java 11 end of life, Java 21 support, Java 
  17 …
 - Basil willing to create that blog post when ready
 - Aligning towards a general plan, good to communicate it later 
 this month
  - Prototype.js removed from Jenkins 2.426 
   <https://www.jenkins.io/blog/2023/05/12/removing-prototype-from-jenkins/> 3 
   Oct 2023
  - 6 months of work <https://issues.jenkins.io/browse/JENKINS-70906> from 
  Tim Jacomb, Basil Crow, and many others
  - Google sheet 
  
<https://docs.google.com/spreadsheets/d/1dpaKALZaK0_HIGy6ony3wnegr1frTg3u1lngG4KdoC8/edit#gid=0>
 shows 
  good status
  - Exceptions mostly from plugins that integrate to company services 
  and are maintained by the company providing the service
 - JFrog Artifactory plugin 
 <https://issues.jenkins.io/browse/JENKINS-71671> not yet released 
 - 23k installs
 - CyberRes Fortify plugin 
 <https://issues.jenkins.io/browse/JENKINS-71303> not yet released 
 - 4k installs
 - XRay test management plugin 
 <https://github.com/jenkinsci/xray-connector-plugin/issues/75> not 
 yet released - 2k installs
 - Synopsys Coverity plugin 
 <https://issues.jenkins.io/browse/JENKINS-71308> not yet released 
 - 1.5k installs
 - Tricentis qTest plugin 
 <https://issues.jenkins.io/browse/JENKINS-71309> not yet released 
 - 1.3k installs
  
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Mark add “Budget and Costs” to regular board meeting agenda (done)
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - Timeline
 - Nomination of candidates (September 18 - October 27)
 - Voter registration (September 18 - November 05)
 - Voting (November 06 - December 1)
 - Results announcement (December 11)
  - Alexander Brandes documented how to nominate someone 
  <https://www.jenkins.io/project/election-walkthrough/>, and how CIVS 
  works <https://www.jenkins.io/project/election-walkthrough/#voting>; 
  both for voters and the election committee
  - Waiting for additional nominations for officers and board members
     - Need more voters to register
 - Encourage fellow contributors to register
  - Mark Waite retrospective on signing certificate renewal process 
   
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
 and 
   its improvements
  - Code signing certificate update for MSI and WAR files
  - PGP signing key update for RPM and DEB files
 - Debian key packaging improvements (some other projects use that 
 technique now)
 - Notification and process improvements
- Reimbursement improvements
 - Details being gathered in the retrospective document 
     
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site - deadline for 4 weeks to close (Kevin 
   Martens)
  - Chinese site link removed from www.jenkins.io header
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
  

Re: Two week break in LTS schedule at end of 2023

[Mark Waite]

Sad that I made so many date related mistakes in a mail message focused on 
dates.  Corrections below:

On Monday, October 16, 2023 at 8:12:50 AM UTC-6 Mark Waite wrote:

I've been assuming a two week break in the LTS schedule at the end of 2023 
as we've done in the past.  That assumption is embedded in the Jenkins 
enhancement proposal for the 2+2+2 Java Support Plan 
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
.

The dates with a two week break would be:


   - 
   
   Nov 15, 2023 - Jenkins 2.426.1 release
   - 
   
   Dec 13, 2024 - Jenkins 2.426.2 release
   

* Dec 13, *2023* - Jenkins 2.426.2 release
 


   - 
   
   Jan 24, 2024 - Jenkins 2.426.3 release (assuming two week skip for 
   holidays
   

With that two week break, Oct 2, 2023 would be the last LTS version to 
support Java 11, with the first LTS version to require Java 17 on Oct 30, 
2024.


With that two week break, *Oct 2, 2024* would be the last LTS version to 
support Java 11, with the first LTS version to require Java 17 on Oct 30, 
2024.
 

The two week break also makes it easier for those who are taking time off 
at the end of the year.

Are there strong objections to the Jenkins project taking the customary two 
week break at the end of the 2023 calendar year? Weekly releases will 
continue during that time, but the time between 2.426.2 and 2.426.3 will 
increase from 4 weeks to 6 weeks.


 

-- 
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/3375231b-aa63-4efa-a55d-3bc20ccbc56en%40googlegroups.com.

Two week break in LTS schedule at end of 2023

[Mark Waite]

I've been assuming a two week break in the LTS schedule at the end of 2023 
as we've done in the past.  That assumption is embedded in the Jenkins 
enhancement proposal for the 2+2+2 Java Support Plan 
<https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11>
.

The dates with a two week break would be:


   - 
   
   Nov 15, 2023 - Jenkins 2.426.1 release
   - 
   
   Dec 13, 2024 - Jenkins 2.426.2 release
   - 
   
   Jan 24, 2024 - Jenkins 2.426.3 release (assuming two week skip for 
   holidays
   

With that two week break, Oct 2, 2023 would be the last LTS version to 
support Java 11, with the first LTS version to require Java 17 on Oct 30, 
2024.

The two week break also makes it easier for those who are taking time off 
at the end of the year.

Are there strong objections to the Jenkins project taking the customary two 
week break at the end of the 2023 calendar year? Weekly releases will 
continue during that time, but the time between 2.426.2 and 2.426.3 will 
increase from 4 weeks to 6 weeks.

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/88fc4e85-9a7e-4166-a5c6-02e3254abbedn%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

I've created a Jenkins Enhancement Proposal based on this draft.  Comments 
are welcomed at https://github.com/jenkinsci/jep/pull/400

On Monday, September 25, 2023 at 7:18:40 AM UTC-6 Mark Waite wrote:

> Java releases are delivered every 6 months with a long term support 
> release every two years as announced in a September 2021 blog post 
> <https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.
>   
> The release cadence is described in more detail in another blog post 
> <https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
> The OpenJDK project and Eclipse Temurin project both support their long 
> term support releases with security patches for six years.
>
> The two year release cadence with a six year support life means that three 
> Java LTS releases are officially supported at any point in time by the 
> OpenJDK project and the Eclipse Temurin project.  Jenkins developers would 
> like to generally support two Java LTS releases rather than three LTS 
> releases in order to reduce overhead from supporting Java releases.
>
> In order to limit Java support to two LTS releases, I propose that the 
> Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
> supported for two years, then becomes the minimum required Java version for 
> two years, then is unsupported for two years.  In the last two years, new 
> Jenkins releases will not run on that oldest supported Java version.
>
> A diagram 
> <https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
>  
> is provided to describe the transition from our current model to the 
> “2+2+2” model.
>
> The diagram shows that as part of the transition, Java 17 will be the 
> minimum required Java version for only 12 months and Java 21 will be the 
> minimum required version for only 18 months.  Java 25 and later will be the 
> minimum required version for 24 months.
>
> The “2+2+2” pattern balances the needs of large scale Jenkins users for 
> predictability and stability and the needs of Jenkins developers for less 
> maintenance overhead.
>
> After a week or two of discussion in the Jenkins developer mailing list 
> and the Jenkins user mailing list, I plan to submit this as a Jenkins 
> Enhancement Proposal.
>
> More details are available in the Google Doc 
> <https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
> .
>
> Thanks,
> 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/56c75c6e-6b94-47cb-8659-a3e1c9df449fn%40googlegroups.com.

Re: 2.426 as Nov 15, 2023 LTS baseline?

[Mark Waite]

Tim Jacomb, can you confirm that 2.426 is approved as the next LTS baseline?

Thanks,
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/78b4cbe6-824e-4d9f-b561-37323b0a1b24n%40googlegroups.com.

Re: Plugin adoption request

[Mark Waite]

On Tuesday, October 10, 2023 at 6:37:50 AM UTC-6 Benoît Le Gall wrote:


*LE GALL Benoît*
*Conception & Development*
This e-mail is intended for the above-mentioned addressees only. It may 
contain privileged or confidential information, the review, dissemination 
or disclosure of which is strictly prohibited. If you have received this 
e-mail by mistake please immediately destroy it and so inform us by e-mail. 


-- Forwarded message -
De : *Benoît Le Gall* 
Date: mar. 10 oct. 2023 à 12:07
Subject: Plugin adoption request
To: Jenkins 


Hi

please note my request for plugin adoption 


   - Link to a plugin you want to adopt => 
   https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin
   - The status of the plugin => "abandoned"
   - Link(s) to pull requests you want to deliver, if applicable => PR#17 
   
<https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin/pull/17>
   - Your GitHub username/id => FrogDevelopper 
   <https://github.com/FrogDevelopper>
   - Your Jenkins infrastructure account id => legall_benoit
   - The link to the "Repository Permission Updater" PR => PR#1 
   <https://github.com/FrogDevelopper/repository-permissions-updater/pull/1>


I'm not sure that all the required tasks are correctly done (about CD and 
automated release in particular), so please don't hesitate to tell me what 
is incorrect


Thanks for being willing to adopt a plugin.  That's great!  The repository 
permissions updater pull request is submitted to your own repository 
instead of being submitted to the upstream repository.  You need to submit 
a pull request to the upstream repository.

Mark Waite
 

*LE GALL Benoît*
*Conception & Development*
This e-mail is intended for the above-mentioned addressees only. It may 
contain privileged or confidential information, the review, dissemination 
or disclosure of which is strictly prohibited. If you have received this 
e-mail by mistake please immediately destroy it and so inform us by e-mail. 

-- 
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/fe494dc0-5fbc-4579-98bd-97b1e2175542n%40googlegroups.com.

Re: 2.426 as Nov 15, 2023 LTS baseline?

[Mark Waite]

On Wednesday, October 4, 2023 at 9:28:38 AM UTC-6 Basil wrote:

+1 

We'll likely need to backport the fix for JENKINS-71937.


I think that we'll also need  to backport the fix for JENKINS-72026  
, though a fix pull request 
has not been submitted yet.

-- 
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/1bad9227-ba20-4c48-8acd-b4b114130c86n%40googlegroups.com.

2.426 as Nov 15, 2023 LTS baseline?

[Mark Waite]

Wednesday, 4 Oct 2023 is listed as the day when we select the baseline for 
the long term support release that will be delivered November 15, 2023.

I propose Jenkins 2.426 <https://www.jenkins.io/changelog/#v2.426> as the 
next LTS baseline.  It removes Prototype.js from Jenkins core and adds the 
Java 11 end of life administrative monitor to warn users that Jenkins will 
no longer support Java 11 after September 30, 2024.

I've updated my development environment to run Jenkins 2.426 with JDK 21.  
I've found no issues in the testing that I've performed.

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/b32ddc69-d333-4b04-aedb-ac491b6a49ebn%40googlegroups.com.

October 2, 2023 Governance Board Agenda

[Mark Waite]

Agenda

 Comment
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#News>News
   
   - Jenkins elections 2023 nominations in progress - Alexander Brandes and 
   Ulli Hafner
  - Announced by blog post 
  
<https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/>
  , community post 
  
<https://community.jenkins.io/t/jenkins-board-and-officer-election-2023/9644>
  , tweet <https://twitter.com/jenkinsci/status/1703772922593132972>, 
  LinkedIn 
  
<https://www.linkedin.com/feed/update/urn:li:activity:7109540080251244546>, 
  and jenkins-infra <https://github.com/jenkins-infra>
   - Cloudflare sponsors Jenkins project
  - Project to host update center content on Cloudflare R2 buckets 
  worldwide
 - Reduce AWS costs for the Jenkins project
  - Java 21 released <https://openjdk.org/projects/jdk/21/> September 
   19, 2023
  - Summary blog post with Java 11 end of life, Java 21 support, Java 
  17 …
 - Basil willing to create that blog post when ready
  - Prototype.js will be removed from Jenkins 2.426 
   <https://www.jenkins.io/blog/2023/05/12/removing-prototype-from-jenkins/> 3 
   Oct 2023
  - 6 months of work <https://issues.jenkins.io/browse/JENKINS-70906> from 
  Tim Jacomb, Basil Crow, and many others
  - Google sheet 
  
<https://docs.google.com/spreadsheets/d/1dpaKALZaK0_HIGy6ony3wnegr1frTg3u1lngG4KdoC8/edit#gid=0>
 shows 
  good status
  - Exceptions mostly from plugins that integrate to company services 
  and are maintained by the company providing the service
 - JFrog Artifactory plugin 
 <https://issues.jenkins.io/browse/JENKINS-71671> not yet released 
 - 23k installs
 - CyberRes Fortify plugin 
 <https://issues.jenkins.io/browse/JENKINS-71303> not yet released 
 - 4k installs
 - XRay test management plugin 
 <https://github.com/jenkinsci/xray-connector-plugin/issues/75> not 
 yet released - 2k installs
 - Synopsys Coverity plugin 
 <https://issues.jenkins.io/browse/JENKINS-71308> not yet released 
 - 1.5k installs
 - Tricentis qTest plugin 
 <https://issues.jenkins.io/browse/JENKINS-71309> not yet released 
 - 1.3k installs
 - OpenStack Cloud <https://issues.jenkins.io/browse/JENKINS-71310> 
fixed 
 but unreleased - 900 installs
  - Next LTS baseline selected Wednesday 4 Oct 2023
  - Jenkins 2.426 expected to be a good choice for 15 Nov 2023 LTS
   - Google Summer of Code projects 
   <https://www.jenkins.io/projects/gsoc/#gsoc-2023> for 2023
  - 4 completed successfully
 - GitLab plugin modernization 
 
<https://www.jenkins.io/projects/gsoc/2023/projects/gitlab-plugin-modernization>
 - Docker compose for tutorials 
 
<https://www.jenkins.io/projects/gsoc/2023/projects/docker-compose-build>
 - Adding probes to plugin health score 
 
<https://www.jenkins.io/projects/gsoc/2023/projects/add-probes-to-plugin-health-score>
 - Building jenkins.io with alternate tools 
 
<https://www.jenkins.io/projects/gsoc/2023/projects/alternative-jenkinsio-build-tool>
  - Prototype.js removed from Jenkins core Oct 3, 2023
   - Java 11 end of life monitor enabled Oct 3, 2023 - end of life Oct 31, 
   2024

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - Timeline
 - Nomination of candidates (September 18 - October 27)
 - Voter registration (September 18 - November 05)
 - Voting (November 06 - December 1)
 - Results announcement (December 11)
  - Alexander Brandes documented how to nominate someone 
  <https://www.jenkins.io/project/election-walkthrough/>, and how CIVS 
  works <https://www.jenkins.io/project/election-walkthrough/#voting>; 
  both for voters and the election committee
   - Mark Waite retrospective on signing certificate renewal process 
   
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
 and 
   its improvements
  - Code signing certificate update for MSI and WAR files
  - PGP signing key update for RPM and DEB files
 - Debian key packaging improvements (some other projects use that 
 technique now)
 - Notification and process improvements
- Reimbursement improvements
 - Details being gathered in the retrospective document 
 
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
 

Re: Proposal: Kris Stern to join the release team

[Mark Waite]

On Tuesday, September 26, 2023 at 11:28:28 AM UTC-5 Alexander Brandes wrote:

Hey everyone,

I would like to propose Kris Stern (@krisstern 
<https://github.com/krisstern>) to join the release team.


+1 from me.  Kris has done very well as release lead for several Jenkins 
releases.

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/fa55cf9e-96a0-434f-9016-a1a76f2d6dfbn%40googlegroups.com.

Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

Java releases are delivered every 6 months with a long term support release 
every two years as announced in a September 2021 blog post 
<https://blogs.oracle.com/java/post/moving-the-jdk-to-a-two-year-lts-cadence>.  
The release cadence is described in more detail in another blog post 
<https://blogs.oracle.com/javamagazine/post/java-long-term-support-lts>.  
The OpenJDK project and Eclipse Temurin project both support their long 
term support releases with security patches for six years.

The two year release cadence with a six year support life means that three 
Java LTS releases are officially supported at any point in time by the 
OpenJDK project and the Eclipse Temurin project.  Jenkins developers would 
like to generally support two Java LTS releases rather than three LTS 
releases in order to reduce overhead from supporting Java releases.

In order to limit Java support to two LTS releases, I propose that the 
Jenkins project adopt a “2+2+2” model where a new Java LTS release is 
supported for two years, then becomes the minimum required Java version for 
two years, then is unsupported for two years.  In the last two years, new 
Jenkins releases will not run on that oldest supported Java version.

A diagram 
<https://docs.google.com/spreadsheets/d/1Gc-0yuYOD5u674qnxbPOWhCU5t9viCJukVj_9b-kwAw/edit?usp=sharing>
 
is provided to describe the transition from our current model to the 
“2+2+2” model.

The diagram shows that as part of the transition, Java 17 will be the 
minimum required Java version for only 12 months and Java 21 will be the 
minimum required version for only 18 months.  Java 25 and later will be the 
minimum required version for 24 months.

The “2+2+2” pattern balances the needs of large scale Jenkins users for 
predictability and stability and the needs of Jenkins developers for less 
maintenance overhead.

After a week or two of discussion in the Jenkins developer mailing list and 
the Jenkins user mailing list, I plan to submit this as a Jenkins 
Enhancement Proposal.

More details are available in the Google Doc 
<https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
.

Thanks,
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/2f4e2751-6765-4973-8a05-48d0a7fce8e5n%40googlegroups.com.

Re: remove j-interop and jcifs from core?

[Mark Waite]

On Monday, September 18, 2023 at 3:59:40 PM UTC-6 Basil wrote:

On Mon, Sep 18, 2023 at 4:19 AM James Nord  wrote:
>
> What do you think?

I think this is a great idea. I am doing something similar for the old XML 
Pull Parser 3rd Edition libraries in jenkinsci/jenkins#8503 
<https://github.com/jenkinsci/jenkins/pull/8503>.


I agree wholeheartedly.  Install as a service on Windows is best handled by 
the MSI installer.

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/504c84c7-7b43-4fb3-8b53-4802d5d184bfn%40googlegroups.com.

September 18, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins governance board meets today at 6:00 PM UTC on Zoom.  The Zoom 
URL is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Agenda <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#News>

News
   
   - Jenkins elections 2023 have started
  - Announced by blog post 
  
<https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/>
  , community post 
  
<https://community.jenkins.io/t/jenkins-board-and-officer-election-2023/9644>
  , tweet <https://twitter.com/jenkinsci/status/1703772922593132972>, 
  LinkedIn 
  
<https://www.linkedin.com/feed/update/urn:li:activity:7109540080251244546>, 
  and jenkins-infra <https://github.com/jenkins-infra>
   - FIPS-140 Jenkins enhancement proposal - JEP-237 
   <https://github.com/jenkinsci/jep/blob/master/jep/237/README.adoc> created 
   by James Nord
   - Java 21 release <https://openjdk.org/projects/jdk/21/> is scheduled 
   for September 19, 2023
  - ci.jenkins.io has Java 21 available and ready to use
  - Jenkins core, plugin BOM, acceptance test harness, and many plugins 
  passing on Java 21
  - Only test changes required for Java 21 thus far (no production 
  issues detected)
   - Prototype.js scheduled to be removed from Jenkins core Oct 3, 2023
   - Java 11 end of life monitor to be enabled Oct 3, 2023 - end of life 
   Oct 31, 2024

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
   
   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - Announced by blog post 
  
<https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/>
  , community post 
  
<https://community.jenkins.io/t/jenkins-board-and-officer-election-2023/9644>
  , tweet <https://twitter.com/jenkinsci/status/1703772922593132972>, 
  LinkedIn 
  
<https://www.linkedin.com/feed/update/urn:li:activity:7109540080251244546>, 
  and jenkins-infra <https://github.com/jenkins-infra>
  - Timeline
 - Nomination of candidates (September 18 - October 27)
 - Voter registration (September 18 - November 05)
 - Voting (November 06 - December 1)
 - Results announcement (December 11)
  - Alexander Brandes documented how to nominate someone 
  <https://www.jenkins.io/project/election-walkthrough/>, and how CIVS 
  works <https://www.jenkins.io/project/election-walkthrough/#voting>; 
  both for voters and the election committee
   - Mark Waite retrospective on signing certificate renewal process 
   
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
 and 
   its improvements
  - Code signing certificate update for MSI and WAR files
  - PGP signing key update for RPM and DEB files
 - Debian key packaging improvements (some other projects use that 
 technique now)
 - Notification and process improvements
- Reimbursement improvements
 - Details being gathered in the retrospective document 
 
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
   - Retire the Chinese Jenkins site - deadline for 4 weeks to close (Kevin 
   Martens)
  - Chinese site link removed from www.jenkins.io header
  - Kevin Martens (Docs Officer) tracking help desk ticket 
  <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
  the Chinese pages with redirects to the English pages
 - Need a redirect from https://www.jenkins.io/zh/ to 
 https://www.jenkins.io/ <https://www.jenkins.io/zh/>
  - Mark Waite draft a proposal to the board for license policy and 
   phrasing changes
  - Allow other licenses like the JSON license
  - Some other approach?
  - What license should be used for a library plugin?
 - License of the wrapped library (if wrapped library has no 
 separate code, then seems likely)
 - MIT license as used by Jenkins plugins (if abstraction layer in 
 the plugin, then MIT for ours?)
  - Mark Waite submit pull request to replace ICRC link with URC link 
   on top page (done and merged 
   <https://github.com/jenkins-infra/jenkins.io/pull/6622>)

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
Topics
   
   - Board and officer elections - Ulli Hafner

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
activity
   
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - Google doc 
  
<https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
 describ

Re: Request for Status Update on Parasoft Findings Plugin 10.6.3 Release

[Mark Waite]

On Friday, September 1, 2023 at 2:38:07 PM UTC-6 Yuqian wrote:

Hi,

This is Yuqian from Parasoft.

I attempted to release the Parasoft Findings Plugin 10.6.3 using "mvn 
release:prepare" and "mvn release:perform." Both commands were successful, 
and I created a corresponding tag:

https://github.com/jenkinsci/parasoft-findings-plugin/releases/tag/parasoft-findings-10.6.3

Could you kindly confirm the progress of this release? It's been two days 
since I initiated it, and I'd appreciate an update.

As far as I can tell, you've created a release in GitHub but have not 
uploaded the binaries to the Jenkins artifact repository.  See the 
instructions 
at https://www.jenkins.io/doc/developer/publishing/releasing-manually/ for 
the steps that you need to perform in order to release manually.

Alternately, you could consider making the switch to automated release as 
described at https://www.jenkins.io/doc/developer/publishing/releasing-cd/

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/3360df4d-2212-4d15-ac5d-3b9b32d56556n%40googlegroups.com.

Re: Adoption of jersey2-api plugin

[Mark Waite]

+1 from me

On Tuesday, August 29, 2023 at 5:08:47 PM UTC-6 Carroll Chiou wrote:

> Hello,
>
> The CloudBees open source team would like to adopt the jersey2-api plugin
>
>- 
>
>Link to a plugin you want to adopt: 
>https://github.com/jenkinsci/jersey2-api-plugin
>- 
>
>The status of the plugin: for-adoption
>- 
>
>Your GitHub username/id: car-roll, jtnord, raul-arabaolaza, rsandell, 
>olamy, julieheard, ampuscas, BorisYaoA 
>- 
>
>Your Jenkins infrastructure account id: carroll, teilo, rarabaolaza, 
>rsandell, olamy, julieheard, ampuscas, borisyaoa
>- 
>
>The link to the "Repository Permission Updater" PR described below: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3505
>
>

-- 
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/8b9c40e4-2be4-4124-bb4c-2a83885b3071n%40googlegroups.com.

Re: Adoption of the GitLab Plugin which has been marked for adoption

[Mark Waite]

+1 from me to add Harsh as a maintainer.  His GSoC work has been a great 
addition to the plugin

On Friday, August 25, 2023 at 11:18:44 AM UTC-6 harshprata...@gmail.com 
wrote:

> Hey folks!
> I would like to adopt the GitLab Plugin - 
> https://github.com/jenkinsci/gitlab-plugin
> My GitHub username : harsh-ps-2003
> My Jenkins infrastructure account username : harsh_ps_2003
> Repository Permission Updater PR link - 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3502
>
> Thanking in Anticipation
> Warm Regards
> Harsh Pratap Singh
>
> On Sunday, 29 January 2023 at 19:56:25 UTC+5:30 kris...@outlook.com wrote:
>
> Hi everyone,
>
> I would like to adopt the GitLab Plugin which has been marked for adoption.
>
>- Link of the plugin: https://github.com/jenkinsci/gitlab-plugin
>- Status of the plugin: "For adoption"
>- My GitHub username/id: krisstern
>- My Jenkins infrastructure account id: krisstern
>- Link to the "Repository Permission Updater" PR: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3106
>
> Appreciate any help possible in this regard!
>
> Best,
> Kris
>
>- 
>
>
>

-- 
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/8ac665e6-1205-47aa-a855-745d1f1a0326n%40googlegroups.com.

August 21, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins governance board meets today at 6:00 PM UTC on Zoom.  The Zoom 
URL is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Action Items
 Comment

   - Alexander Brandes and Ullrich Hafner run the officer and board 
   elections for 2023
  - A timeline has been drafted to plan enough time ahead for every 
  phase.
  - Last year’s timeline was pretty short for each phase.
  - Alexander Brandes documented how to nominate someone, and how the 
  CIVS work; both for voters and the election committee
   - Mark Waite retrospective on signing certificate renewal process 
   
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
 and 
   its improvements
  - Code signing certificate update for MSI and WAR files
  - PGP signing key update for RPM and DEB files
 - Debian key packaging improvements (some other projects use that 
 technique now)
 - Notification and process improvements
- Reimbursement improvements
 - Details being gathered in the retrospective document 
 
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
  - Mark Waite submit jenkins.io pull request to combine subprojects 
   and SIGs into a single concept - “working groups”
  - More pull requests needed
  - Retire the Chinese Jenkins site
 - Chinese site link removed from www.jenkins.io header
 - Kevin Martens (Docs Officer) tracking help desk ticket 
 <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace 
 the Chinese pages with redirects to the English pages
- Need a redirect from https://www.jenkins.io/zh/ to 
https://www.jenkins.io/ <https://www.jenkins.io/zh/>
 - Related to upgrading HTMLUnit and modernizing plugins: Basil 
 deprecated the translation assistance plugin (years out of date)
- Servers providing that facility are shutdown (long ago)
   - Could still use the plugin locally to submit to the local 
   Jenkins instance, but can’t contribute back to the plugin

<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA#Governance-Topics>Governance 
Topics
   
   - Licensing of libraries
  - JSON library - see the Jenkins developer mailing list 
  <https://groups.google.com/g/jenkinsci-dev/c/POxcfeUTRzo/m/iGHzTpmMAgAJ>
  - Other libraries - see the Jenkins board mailing list 
  <https://groups.google.com/g/jenkinsci-board/c/j1PMBQb_e14>
   - GitHub two factor authentication for many members of jenkinsci 
   organization
  - Message 
  
<https://groups.google.com/g/jenkinsci-board/c/--ZYtPMyfMQ/m/kAru1mRwBwAJ?utm_medium=email_source=footer>
 from 
  Alexander Brandes
   - Switch jenkins.io from International Committee for the Red Cross to 
   another recommendation
  - Ticket on jenkins.io issue tracker 
  <https://github.com/jenkins-infra/jenkins.io/issues/6584>
   
<https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA#Community-activity>Community 
activity
   
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - Google doc 
  
<https://docs.google.com/document/d/1y3RVlniNmz-5Nd3LI-w58LDf760Ai7FqssP4zHuTv8U/edit?usp=sharing>
 describes 
  plan that has been discussed with Jenkins board and Jenkins officers
  - Ready to discuss more widely in the community
 - Jenkins developers mailing list
 - Jenkins users mailing list
 - Jenkins enhancement proposal?
  - Key dates upcoming
 - Oct 3, 2023 - Java 11 end of life monitor visible in Jenkins 
 weekly
 - Oct xx, 2023 - Java 21 supported by Jenkins core and many plugins
 - Dec 13, 2023 - Java 11 end of life monitor visible in Jenkins LTS
 - Aug 7, 2024 - Last Jenkins LTS release to support Java 11
 - Sep 4, 2024 - First Jenkins LTS to require Java 21
  - Artifactory bandwidth reduction project https://repo.jenkins-ci.org
  - JFrog has asked that we switch our mirrored repositories (repo-1, 
  jgit, etc.) from public to private so that they are not misused as caches 
  by others
  - Changes to be evaluated to test the switch
 - Adjust parent poms to declare multiple repositories
  - Prototype.js removal blog post 
   <https://www.jenkins.io/blog/2023/05/12/removing-prototype-from-jenkins/> 
guides 
   new contributors
  - Oct 3, 2023 proposed as the date to remove Prototype.js from 
  Jenkins core 
  <https://github.com/jenkinsci/jenkins/pull/7781#issuecomment-1679658280>
  - Prototype.js removal epic 
  <https://issues.jenkins.io/browse/JENKINS-70906> making progress
  - Plugin progress visible in the tracking sheet 
  
<https://docs.google.com/spreadsheets/d/1dpaKALZaK0_HIGy6ony3wnegr1frTg3u1lngG4KdoC8/edit?usp=sharing>
  - Mo

Re: commit access lost to blueocean-plugin

[Mark Waite]

The lockout on repo.jenkins-ci.org has happened to several of us.  An 
Artifactory admin will need to toggle a setting on your account on 
repo.jenkins-ci.org

I don't understand the block on GitHub/  Have you tried ssh access rather 
than https?

On Tuesday, August 1, 2023 at 7:47:24 PM UTC-6 olive...@gmail.com wrote:

> and my account seems to be locked on https://repo.jenkins-ci.org/
> while I can still log in to issues.j.o
>
> definitely not a good day :)
>
>
>
> On Wed, 2 Aug 2023 at 10:53, Olivier Lamy  wrote:
> >
> > Hi,
> > Until yesterday, I was able to push to blueocean-plugin repo but this
> > morning (2 Aug) this does not work anymore
> >
> > olamy@pop-os:~/dev/sources/jenkins/blueocean-plugin$ git push origin
> > snakeyaml-2.0
> > remote: Permission to jenkinsci/blueocean-plugin.git denied to olamy.
> > fatal: unable to access
> > 'https://github.com/jenkinsci/blueocean-plugin/': The requested URL
> > returned error: 403
> >
> >
> > did something change recently?
> >
> > thanks
> > --
> > Olivier
>
> --
> Olivier
>

-- 
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/5f6d811e-256a-440e-b731-557d041f3826n%40googlegroups.com.

Re: 401 from repo.jenkins-ci.org

[Mark Waite]

On Wednesday, July 26, 2023 at 1:20:36 PM UTC-6 Tomas wrote:

I was unable to release my plugin:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/release.sh

[INFO] [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy (default-deploy) 
on project generic-webhook-trigger: Failed to deploy artifacts: Could not 
transfer artifact org.jenkins-ci.plugins:generic-webhook-trigger:pom:1.86.6 
from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases): 
authentication failed for 
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/generic-webhook-trigger/1.86.6/generic-webhook-trigger-1.86.6.pom,
 
status: 401 Unauthorized -> [Help 1]

Tried the curl command, gave me 401:

curl -u "tomasbjerre:X" https://repo.jenkins-ci.org/setup/settings.xml
{
  "errors" : [ {
"status" : 401,
"message" : "Bad credentials"
  } ]

Logged on to https://accounts.jenkins.io/myself/ and changed the password, 
still same with the curl command.

Temporary problem?


Ulli Hafner had a similar problem today.  His issue was resolved when a 
repository administrator changed a setting on his account on the 
repository.  May be best for you to open an infra help desk ticket 
like https://github.com/jenkins-infra/helpdesk/issues/3680 

-- 
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/e0d42289-c37b-46cf-a816-0ad4dbb446c2n%40googlegroups.com.

Re: JSON license

[Mark Waite]

On Tuesday, July 25, 2023 at 4:24:04 PM UTC-6  Filipe Roque wrote:

I have not found any discussion on the mailing list about this. 

JSON License has not been considered an open source license by Apache [1], 
Debian [2] and FSF [3] and is not OSI approved [4]. 

Douglas Crockford has relicensed org.json:json java library to be Public 
Domain starting with version 20220924 [5]. 

Jenkins requires plugins and its dependencies to be free and open source 
software [6][7].

I did some analysis on the latest Jenkins plugins usage of org.json:json 
[8]. I have found a total of 473 plugins that depend on org.json:json 
(directly or transitively), with 104 plugins being free versions, 67 
plugins directly depend on non free versions of org.json:json. 

Is this an actual concern for the Jenkins project ? If so, how to proceed ?


I think it is a concern for the Jenkins project.  Thanks for noting the 
issue.  I don't think the risk is high, but it is a concern that is worth 
some effort to assure that Jenkins remains free and open source.

I believe one concern is related to software that is in the public domain 
not using an OSI approved license.  We could extend the definition of 
licenses accepted by the Jenkins project to include OSI approved licenses 
and public domain software.  That would address the concerns of those who 
worry that "public domain" is not a license.

The other concern is how do we reduce the number of versions and encourage 
use of the public domain version instead of the not quite OSI approved 
license of the earlier versions.  I think that Basil's observation that 
the org.json:json should be made into a library plugin is the way to reduce 
the number of versions and encourage use of the public domain version.

With regards to the list of plugins, only 7 of the 67 plugins that directly 
depend on versions prior to 20220924 have more than 1000 installations.  
Those seem like the first candidates to consider for either an upgrade of 
the library version or replacement of the library dependency with a plugin 
dependency.

With regards to the analysis, I'm not confident in my understanding of the 
specific details of the analysis.  Maybe you can help me understand more 
clearly.

I maintain the elastic axis plugin and it is on the list as having a 
transitive dependency on an older version of the json library.  The elastic 
axis plugin depends on the matrix project plugin.  The matrix project 
plugin depends on the junit plugin.  The junit plugin depends on the 
jackson2 api plugin.  The jackson2 api plugin bundles the jackson2 api jar 
file and the json-20230227.jar inside its hpi file.  I think that would 
cause jackson2 api calls to use the the json-20230227.jar that is bundled 
in the hpi file.

However, the analysis indicates that there is a dependency on 
json-20190722.  Is the analysis not detecting that the jackson2 api plugin 
already includes a newer version of the json library?  Am I 
misunderstanding how libraries are resolved?

I'll put the topic on the next agenda for the Jenkins governing board.

Thanks,
Mark Waite
 


Filipe Roque

[1] https://lwn.net/Articles/707510/
[2] https://wiki.debian.org/qa.debian.org/jsonevil
[3] https://www.gnu.org/licenses/license-list.html#JSON
[4] https://opensource.org/licenses/
[5] https://github.com/stleary/JSON-java/issues/686
[6] https://www.jenkins.io/doc/developer/publishing/preparation/#license
[7] 
https://www.jenkins.io/project/governance/#3rd-party-library-licenses-in-the-plugins
[8] 
https://docs.google.com/spreadsheets/d/1MWNi796iAovFa6GK7LJ0gilbQRwvb8Su3c7YgpH_fuc/edit?usp=sharing

-- 
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/d84bbf01-6d3c-495c-81fb-a715377c89e4n%40googlegroups.com.

July 24, 2023 Governance Board Agenda

[Mark Waite]

The Jenkins governance board meets today at 6:00 PM UTC on Zoom.  The Zoom 
URL is https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Current meeting agenda is:

 

Agenda:

   - 
   
   News
   - 
  
  Releases
  - 
 
 Jenkins 2.401.3 released Wednesday July 26, 2023
 - 

Security release as announced in Jenkins advisories mailing list 

<https://groups.google.com/g/jenkinsci-advisories/c/2GiSsACaT28/m/BCIjzsneBQAJ>,
 
includes 2.416
- 

Merges are paused to the master branch of Jenkins core until 
after the release
- 
 
 Jenkins 2.414 is the next LTS baseline
 - 

Jenkins 2.414.1 release candidate Aug 9, 2023
- 

Jenkins 2.414.1 release Aug 23, 2023
- 
   
   Action Items
   - 
  
  Mark Waite archive the governance meeting notes to a GitHub 
  repository, use the Google doc as the working document, then publish 
final 
  notes (done)
  - 
 
 Mark archive submitted to the governance meeting archives 
 repository 
 <https://github.com/jenkins-infra/governance-meetings-archives/> 
 in a merged pull request 
 <https://github.com/jenkins-infra/governance-meetings-archives/pull/10>
  
 

   - 
   
   NEW Alexander Brandes : Thoughts about using 
   HackMD (https://hackmd.io/team/jenkins-governance 
   (https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA)) as a living document, like the 
   infra team does?
   
Then we could push meeting minutes directly to GitHub and retire the google 
doc totally.

   - 
   
   Mark Waite retrospective on signing certificate renewal process 
   
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
 
   and its improvements
   - 
  
  Code signing certificate update for MSI and WAR files
  - 
  
  PGP signing key update for RPM and DEB files
  - 
 
 Debian key packaging improvements (some other projects use that 
 technique now)
 - 
  
  Notification and process improvements
  - 
 
 Reimbursement improvements
 - 
  
  Details being gathered in the retrospective document 
  
<https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
  - 
   
   Mark Waite submit jenkins.io pull request to combine subprojects and 
   SIGs into a single concept - “working groups”
   - 
  
  More pull requests needed
  

   - 
   
   Jenkins board and officer elections in November 2023
   - 
      
  Proposal: Mark Waite and Alexander Brandes run the 2023 elections 
  using same process as last year
  - 
   
   Community activity
   - 
  
  Artifactory bandwidth reduction project
  - 
 
 JFrog hosts https://repo.jenkins-ci.org and covers all costs for 
 the Jenkins project
 - 

JFrog is happy to continue hosting and sponsoring 
https://repo.jenkins-ci.org 
- 
 
 Bandwidth use has been excessive due to abuse and misuse of its 
 services
 - 

Duplicate downloads of released artifacts (jenkins.war, some 
tool installers)
- 
 
 20 TB per month saved by blocking IP address of one abuser (March 
 2023)
 - 
 
 JFrog has asked us to password protect our mirrors for the next 
 reduction in bandwidth
 - 

Mark Waite’s proposal is described in detail in the help desk 
ticket 

<https://github.com/jenkins-infra/helpdesk/issues/3599#issuecomment-1640551729>
- 
 
 Action: Mark scheduling a discussion session this week with 
 Jenkins infra, Jenkins security, and others
 - 

Damien Duportal, Daniel Beck, James Nord, Stephane Merle, Herve 
LeMeur
- 

Other are welcome to attend
- 
  
  Prototype.js removal blog post 
  <https://www.jenkins.io/blog/2023/05/12/removing-prototype-from-jenkins/> 
  guides new contributors
  - 
 
 Prototype.js removal epic 
 <https://issues.jenkins.io/browse/JENKINS-70906> making progress
 - 
 
 Plugin progress visible in the tracking sheet 
 
<https://docs.google.com/spreadsheets/d/1dpaKALZaK0_HIGy6ony3wnegr1frTg3u1lngG4KdoC8/edit?usp=sharing>
 - 
 
 Concern for company maintained plugins to services we cannot test 
 ourselves
 - 

   

Re: GitSCM is marked as Serializable but can't be serialized because of GitSCM.extensions

[Mark Waite]

On Sunday, July 16, 2023 at 4:43:18 AM UTC-6 Reda wrote:

Hi everyone,

I'd like to understand how am I supposed to handle *GitSCM* in a 
*StepExecution*.

Here is the interesting portion of the code : 
https://github.com/jenkinsci/git-push-plugin/blob/5c9525da6da7bed8fd70e8a45d62eafd1daad3f1/src/main/java/io/jenkins/plugins/git_push/GitPushStep.java#L71-L71

If I remove the *transient* modifier from the *GitScm *attribute, I will 
get *java.io.NotSerializableException: hudson.util.DescribableList*.

Is GitPushStep already doing that correctly? If yes, what are the 
consequences of this lack of serialization?


GitSCM is not serializable.  It is correct to not attempt to serialize it.  
Can you explain why you believe that you need to serialize it? 

-- 
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/71e7ba65-cc4a-473f-813e-2c631288bcean%40googlegroups.com.

Re: Jenkins 2.413 as next LTS baseline?

[Mark Waite]

On Monday, July 17, 2023 at 9:41:51 AM UTC-6 Basil Crow wrote:

There do not appear to be any known user-visible regressions in production 
code in 2.414, but jenkinsci/jenkins#7872 
<https://github.com/jenkinsci/jenkins/pull/7872> implies a change in Login 
Theme (3,757 installations) which has not yet been completed (tracked in 
JENKINS-71238 <https://issues.jenkins.io/browse/JENKINS-71238>) and 
jenkinsci/jenkins#7942 <https://github.com/jenkinsci/jenkins/pull/7942> 
implies a change in Calendar View (1,866 installations) which has not yet 
been completed (tracked in JENKINS-71663 
<https://issues.jenkins.io/browse/JENKINS-71663>). If these tasks are not 
completed by the time 2.414 LTS ships, they should be documented as known 
defects in the release notes.


Thanks for noting those needed additions to the upgrade guide.  Since those 
changes are in Jenkins 2.413 and in Jenkins 2.414, it makes sense to me 
that we choose Jenkins 2.414.

Tim Jacomb, do you agree that Jenkins 2.414 should be the baseline for the 
LTS release scheduled for August 23, 2023?

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/2fad8aa3-2774-413d-b41b-1f2e1ee1a94dn%40googlegroups.com.

Re: New Plugin version not updated on Jenkins IO Plugin page

[Mark Waite]

On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote:

Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have 
send you the previous email. It is all set now.

Just for reference on the next update: the 1.2.0 version took over 6hr to 
show up on https://plugins.jenkins.io/, while 1.2.1 showed up after 1 hr. 
It is just the time that the batch process ran to update the wiki page (~ 6 
hours)?


No, that's just the "luck of the draw" for the times when the plugins site 
is rebuilt.  I believe it is rebuilt approximately every 6 hours.
 

-- 
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/0199409d-3e9d-4966-afbe-6fdf6ece0ba1n%40googlegroups.com.