Add 2.541.x line, remove 2.504.x line by shalinisudarsan · Pull Request #6198 · jenkinsci/bom

shalinisudarsan · 2026-01-08T01:19:55Z

Added 2.541.x line, and removed 2.504.x line

Follows the same pattern as prior pull request:

Add 2.528.x release line, remove 2.492.x release line #5713

Testing done

LINE=2.541.x PLUGINS=git-client TEST=InjectedTest bash ./local-test.sh

Submitter checklist

Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
Ensure that the pull request title represents the desired changelog entry
Please describe what you did
Link to relevant pull requests, esp. upstream and downstream changes
~~Link to relevant issues in GitHub or Jira~~
~~Ensure you have provided tests that demonstrate the feature works or the issue is fixed~~

krisstern · 2026-01-08T07:38:08Z

@dduportal @MarkEWaite Do you guys have any insight as to where the errors are coming from?

alecharp · 2026-01-08T08:15:46Z

This looks like an issue with caching the artifacts. cc @lemeurherve

krisstern · 2026-01-08T08:18:10Z

Thanks for the checking @alecharp!

lemeurherve · 2026-01-08T12:42:05Z

Thanks for the heads-up @alecharp @krisstern, will take a closer look when possible.

I've restarted a build without ACP meanwhile.

lemeurherve · 2026-01-08T13:25:54Z

@shalinisudarsan @krisstern FYI the error is not related to ACP.

From https://ci.jenkins.io/job/Tools/job/bom/job/PR-6198/4/pipeline-overview/?start-byte=5081031&selected-node=22#log-22-1112 which ran without ACP:

[ERROR] Non-resolvable import POM: The following artifacts could not be resolved: io.jenkins.tools.bom:bom-2.541.x:pom:5877.vd5b_02d3951a_9 (absent): Could not find artifact io.jenkins.tools.bom:bom-2.541.x:pom:5877.vd5b_02d3951a_9 in repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/) @ io.jenkins.tools.bom:sample:${changelist}, /home/jenkins/agent/workspace/Tools_bom_PR-6198/sample-plugin/pom.xml, line 22, column 19

lemeurherve · 2026-01-08T13:28:28Z

Do you guys have any insight as to where the errors are coming from?

Can you post the actual error the next times please?

It could be quite helpful, especially since builds are cleaned up afterward: the previous logs may not be available later.

jglick · 2026-01-08T13:41:28Z

Note that JUnit test failures are normally preserved in GH Checks even after the Jenkins build has been deleted. Failing sh steps may be too, but with truncation.

alecharp · 2026-01-08T19:43:45Z

Can you post the actual error the next times please?

I know it's no proof but running the command that failed on the build locally worked just fine.

lemeurherve · 2026-01-08T20:26:35Z

Can you post the actual error the next times please?

I know it's no proof but running the command that failed on the build locally worked just fine.

The later doesn't prevent the former 😉

Having the error logs (or at least an extract) directly in a bug report is more useful than just stating that "it doesn't work": less back and forth, more efficient for everyone.

I know it's no proof but running the command that failed on the build locally worked just fine.

In retrospect, also a detail (what has been checked) that could have been interesting to mention in the bug report or first comments 🙂

lemeurherve · 2026-01-08T21:02:13Z

Sorry, did not have time to look closer at the error yet.

Do you mind opening an helpdesk issue if you feel it's an infra problem?

MarkEWaite · 2026-01-08T22:51:20Z

I merged the master branch into the pull request and added some additional changes to make the pull request better match with the pull request that added 2.528.x. I did not drop the 2.504.x line (yet), though I think that should be part of this pull request before it is marked as ready for review.

alecharp · 2026-01-09T08:24:53Z

Having the error logs (or at least an extract) directly in a bug report is more useful than just stating that "it doesn't work": less back and forth, more efficient for everyone.

We had nothing more than the "cannot resolve artefact ..."

In retrospect, also a detail (what has been checked) that could have been interesting to mention in the bug report or first comments 🙂

I came later on this subject. I could only test the situation after the fact.

krisstern · 2026-01-09T12:14:32Z

Can you post the actual error the next times please?

@lemeurherve Sure, but the error relevant stack trace was really long

lemeurherve · 2026-01-09T13:12:11Z

Having the error logs (or at least an extract) directly in a bug report is more useful than just stating that "it doesn't work": less back and forth, more efficient for everyone.

We had nothing more than the "cannot resolve artefact ..."

Can you post the actual error the next times please?

@lemeurherve Sure, but the error relevant stack trace was really long

FWIW, here is what I would have expected to be reported from https://ci.jenkins.io/job/Tools/job/bom/job/PR-6198/3/:

08:21:50  + mvn -f sample-plugin clean package -Dset.changelist -P2.541.x
08:21:52  [INFO] Setting: -Dchangelist=5877.vd5b_02d3951a_9 -DscmTag=d5b02d3951a96b7c171911c92002086074be18aa -Dproject.build.outputTimestamp=2026-01-08T01:19:33Z
08:21:52  [INFO] Setting: -DgitHubRepo=shalinisudarsan/bom
08:21:52  [INFO] Scanning for projects...
08:21:53  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
08:21:53  [ERROR] Non-resolvable import POM: The following artifacts could not be resolved: io.jenkins.tools.bom:bom-2.541.x:pom:5877.vd5b_02d3951a_9 (absent): Could not find artifact io.jenkins.tools.bom:bom-2.541.x:pom:5877.vd5b_02d3951a_9 in artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/) @ io.jenkins.tools.bom:sample:${changelist}, /home/jenkins/agent/workspace/Tools_bom_PR-6198/sample-plugin/pom.xml, line 22, column 19

Details

krisstern · 2026-01-11T15:33:20Z

@lemeurherve I am seeing the following in the CI/CD output now:

Error output

pct-ssh-steps-plugin-2.516.x: error in 'sh' step pct-JiraTestResultReporter-plugin-weekly / Checks if running on a Unix-like node Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-active-directory-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-cloudbees-jenkins-advisor-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-command-launcher-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-commons-collections4-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-commons-compress-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-docker-workflow-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-durable-task-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-electricflow-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-email-ext-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-envinject-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-external-monitor-job-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-gitlab-kubernetes-credentials-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-jackson2-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-jaxb-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-json-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-lockable-resources-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-okhttp-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-pam-auth-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-plain-credentials-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-prism-api-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-role-strategy-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-variant-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-workflow-basic-steps-plugin-weekly / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-apache-httpcomponents-client-4-api-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-apache-httpcomponents-client-5-api-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-artifact-manager-s3-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-bouncycastle-api-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-built-on-column-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-cloudbees-jenkins-advisor-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-coverage-badges-extension-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-coverage-plugin-2.516.x / Shell Script
Error in sh step, with arguments mvn -v bash pct.sh.

script returned exit code 1
Build log
pct-database-mysql-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-dockerhub-notification-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-file-parameters-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-gitea-checks-plugin-2.516.x / Shell Script
Error in sh step, with arguments mvn -v bash pct.sh.

script returned exit code 1
Build log
pct-instant-messaging-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-ionicons-api-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-jersey3-api-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-jsch-plugin-2.516.x / Checks if running on a Unix-like node
Error in isUnix step.

Required context class hudson.Launcher is missing
Perhaps you forgot to surround the isUnix step with a step that provides this, such as: node
pct-parameter-separator-plugin-2.516.x / Shell Script
Error in sh step, with arguments mvn -v bash pct.sh.

script returned exit code 1
Build log
pct-ssh-steps-plugin-2.516.x / Shell Script
Error in sh step, with arguments mvn -v bash pct.sh.

script returned exit code 1
Build log

lemeurherve · 2026-01-13T08:59:19Z

@lemeurherve I am seeing the following in the CI/CD output now:
Error output

From the full console log of https://ci.jenkins.io/job/Tools/job/bom/job/PR-6198/9/ searching for "[ERROR]" I saw this:

Details

[2026-01-11T14:37:02.723Z] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.6.2:enforce (display-info) on project gitea-checks: 
[2026-01-11T14:37:02.723Z] [ERROR] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[2026-01-11T14:37:02.723Z] [ERROR] Detected JDK /opt/jdk-17 is version 17.0.17 which is not in the allowed range [21,).
[2026-01-11T14:37:02.723Z] [ERROR] -> [Help 1]
[2026-01-11T14:37:02.724Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.6.2:enforce (display-info) on project gitea-checks: 
[2026-01-11T14:37:02.724Z] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[2026-01-11T14:37:02.724Z] Detected JDK /opt/jdk-17 is version 17.0.17 which is not in the allowed range [21,).
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
[2026-01-11T14:37:02.724Z]     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[2026-01-11T14:37:02.725Z]     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[2026-01-11T14:37:02.726Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
[2026-01-11T14:37:02.726Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
[2026-01-11T14:37:02.726Z]     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
[2026-01-11T14:37:02.726Z]     at java.lang.reflect.Method.invoke (Method.java:569)
[2026-01-11T14:37:02.726Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
[2026-01-11T14:37:02.726Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
[2026-01-11T14:37:02.726Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
[2026-01-11T14:37:02.726Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
[2026-01-11T14:37:02.726Z] Caused by: org.apache.maven.plugin.MojoExecutionException: 
[2026-01-11T14:37:02.726Z] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[2026-01-11T14:37:02.726Z] Detected JDK /opt/jdk-17 is version 17.0.17 which is not in the allowed range [21,).
[2026-01-11T14:37:02.727Z]     at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:272)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
[2026-01-11T14:37:02.727Z]     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[2026-01-11T14:37:02.728Z]     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[2026-01-11T14:37:02.729Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
[2026-01-11T14:37:02.729Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
[2026-01-11T14:37:02.729Z]     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
[2026-01-11T14:37:02.729Z]     at java.lang.reflect.Method.invoke (Method.java:569)
[2026-01-11T14:37:02.729Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
[2026-01-11T14:37:02.729Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
[2026-01-11T14:37:02.729Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
[2026-01-11T14:37:02.729Z]     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)

Also a lot of "Agent was terminated". I restarted a build.

Maybe the branch should be updated, idk.

If you encounter another error that you think is related to the infrastructure itself, can you open an helpdesk please?
(We may miss pings elsewhere, bu we definitely won't miss a new helpdesk)

krisstern · 2026-01-13T09:17:57Z

Yes, sure!

krisstern · 2026-01-14T11:48:49Z

Hi @MarkEWaite @lemeurherve any ideas on the latest batch of errors?

MarkEWaite · 2026-01-14T13:38:57Z

First investigation shows that we need a new release of the sbt plugin to fix the issue discovered in pull request:

Update dependency org.jenkins-ci.main:jenkins-war to v2.546 #6225

krisstern · 2026-01-14T13:52:37Z

@lemeurherve I think there may be a bug on GitHub, as I checked locally there shouldn't be any merge conflicts remaining

lemeurherve · 2026-01-14T14:54:10Z

@lemeurherve I think there may be a bug on GitHub, as I checked locally there shouldn't be any merge conflicts remaining

Maybe but I doubt it.

What did you checked?
What are the commands you tried?

One more time, please try to put more details in your issue reports.
I'd expect more from a seasoned contributor as you.

MarkEWaite · 2026-01-15T12:50:34Z

I've resolved the merge conflicts. The issue with the tests of the sbt plugin are resolved as well.

krisstern · 2026-01-15T14:43:13Z

I realised I was probably was confused about why I needed to commit the removal of the 2.504.x pom.xml file, rebased, and re-removed it again...

krisstern · 2026-01-15T19:22:08Z

I am seeing something regarding the Java JDK version which is causing the remaining 4 plugin test failures:

[2026-01-15T18:20:45.897Z] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion failed with message:
[2026-01-15T18:20:45.897Z] Detected JDK /opt/jdk-17 is version 17.0.17 which is not in the allowed range [21,).

jglick · 2026-01-15T19:34:25Z

@krisstern because for example jenkinsci/ssh-steps-plugin#181 (comment)

krisstern · 2026-01-15T19:58:06Z

Thanks @jglick! Appreciate it

krisstern · 2026-01-18T11:25:57Z

Is there anything I should do regarding the remaining three plugins with failures?

MarkEWaite · 2026-01-18T14:22:54Z

Is there anything I should do regarding the remaining three plugins with failures?

We need a new release of the parameter separator plugin that uses the plugin parent pom that is currently on its master branch. The latest release of the plugin used plugin pom 6.2105.v7d6ddb_2da_0d2 and that has a known problem with the plugin BOM and Java 17. @jonesbusy could you label one of the already merged pull requests as "developer" or "enhancement" or "bug" and start the GitHub action to release a new version?

jonesbusy · 2026-01-18T14:33:55Z

Released on https://github.com/jenkinsci/parameter-separator-plugin/releases/tag/334.v1fc0e534c71d

MarkEWaite · 2026-01-18T14:39:03Z

Is there anything I should do regarding the remaining three plugins with failures?

We need a new release of the parameter separator plugin that uses the plugin parent pom that is currently on its master branch.
The latest release of the plugin used plugin pom 6.2105.v7d6ddb_2da_0d2 and that has a known problem with the plugin BOM and Java 17. @jonesbusy could you label one of the already merged pull requests as "developer" or "enhancement" or "bug" and start the GitHub action to release a new version?

The same seems to apply to coverage plugin and gitea-checks plugin. @uhafner will need to release a new version of coverage plugin and @viceice will need to release a new version of the gitea-checks plugin. I'm not sure if a new release of the analysis-pom will be required for those plugins. @uhafner manages the configuration of the analysis-pom.

uhafner · 2026-01-18T20:52:16Z

I released https://github.com/jenkinsci/coverage-plugin/releases/tag/2.3120.v73353a_97726e. I hope it will work without analysis-pom changes.

Add profile for latest release version 2.541.1

Follows the same pattern as prior pull request: * jenkinsci#5713 Testing done: `LINE=2.541.x PLUGINS=git-client TEST=InjectedTest bash ./local-test.sh`

…7d081847a_ (jenkinsci#6249) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…ci#6250) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…83935f9b_ (jenkinsci#6251) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…enkinsci#6252) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…update-jenkins-version-to-2.541.1

viceice · 2026-01-19T12:14:16Z

released https://github.com/jenkinsci/gitea-checks-plugin/releases/tag/603.621.vc708da_fb_371d
let me know if something is still missing 🤗

…update-jenkins-version-to-2.541.1

shalinisudarsan requested a review from a team as a code owner January 8, 2026 01:19

shalinisudarsan changed the title ~~Add profile for latest release version 2.541.1~~ Test profile for latest release version 2.541.1 Jan 8, 2026

shalinisudarsan mentioned this pull request Jan 8, 2026

LTS 2.541.1 release checklist jenkins-infra/release#811

Closed

51 tasks

shalinisudarsan marked this pull request as draft January 8, 2026 01:25

krisstern added the full-test Test all LTS lines in this PR and do not halt upon first error. label Jan 8, 2026

krisstern changed the title ~~Test profile for latest release version 2.541.1~~ Test profile for latest release version 2.541.1 RC Jan 8, 2026

lemeurherve added the skip-artifact-caching-proxy Do not use artifact caching proxy on this pull request label Jan 8, 2026

lemeurherve removed the skip-artifact-caching-proxy Do not use artifact caching proxy on this pull request label Jan 8, 2026

MarkEWaite changed the title ~~Test profile for latest release version 2.541.1 RC~~ Add 2.541.x line, remove 2.504.x line Jan 9, 2026

krisstern mentioned this pull request Jan 9, 2026

[RELEASE] New release for 2026-01-09 #6190

Closed

12 tasks

dduportal mentioned this pull request Jan 13, 2026

ci.jenkins.io is responding slowly jenkins-infra/helpdesk#4894

Closed

krisstern force-pushed the chore/update-jenkins-version-to-2.541.1 branch from fc02fa3 to 332da9b Compare January 13, 2026 16:14

MarkEWaite mentioned this pull request Jan 15, 2026

Artifact caching proxy fails with 'No route to host' on Jenkins core build jenkins-infra/helpdesk#4946

Closed

shalinisudarsan and others added 8 commits January 19, 2026 05:00

Add profile for latest release version 2.541.1

ee6d0fb

Add profile for latest release version 2.541.1

Add 2.541.x line

43be9af

Follows the same pattern as prior pull request: * jenkinsci#5713 Testing done: `LINE=2.541.x PLUGINS=git-client TEST=InjectedTest bash ./local-test.sh`

Remove 2.504.x line

5f5bd2b

Document 5888.vd99c2b_38128d as last release of 2.504.x line

bc850a4

Update dependency io.jenkins.plugins:flyway-api to v11.20.2-404.v5a_3…

f5474df

…7d081847a_ (jenkinsci#6249) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Update dependency org.jenkins-ci.tools:git-parameter to v462 (jenkins…

50d466e

…ci#6250) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Update dependency org.jenkins-ci.plugins:ssh-steps to v2.0.92.vb_a_05…

1ec717d

…83935f9b_ (jenkinsci#6251) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Update dependency org.jenkins-ci.plugins:pipeline-build-step to v584 (j…

9637fde

…enkinsci#6252) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

krisstern force-pushed the chore/update-jenkins-version-to-2.541.1 branch from 08998ea to 9637fde Compare January 18, 2026 21:01

Merge branch 'master' of https://github.com/jenkinsci/bom into chore/…

4b2bef2

…update-jenkins-version-to-2.541.1

Merge branch 'master' of https://github.com/jenkinsci/bom into chore/…

871a1f0

…update-jenkins-version-to-2.541.1

shalinisudarsan closed this Jan 21, 2026

shalinisudarsan deleted the chore/update-jenkins-version-to-2.541.1 branch January 21, 2026 15:21

shalinisudarsan mentioned this pull request Jan 21, 2026

Add 2.541.x line and remove 2.504.x #6285

Merged

6 tasks

krisstern mentioned this pull request Mar 30, 2026

Add 2.555.x line, remove 2.516.x line #6540

Merged

6 tasks

Uh oh!

Conversation

shalinisudarsan commented Jan 8, 2026 • edited by krisstern Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Testing done

Submitter checklist

Uh oh!

krisstern commented Jan 8, 2026

Uh oh!

alecharp commented Jan 8, 2026

Uh oh!

krisstern commented Jan 8, 2026

Uh oh!

lemeurherve commented Jan 8, 2026

Uh oh!

lemeurherve commented Jan 8, 2026

Uh oh!

lemeurherve commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jglick commented Jan 8, 2026

Uh oh!

alecharp commented Jan 8, 2026

Uh oh!

lemeurherve commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lemeurherve commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MarkEWaite commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

alecharp commented Jan 9, 2026

Uh oh!

krisstern commented Jan 9, 2026

Uh oh!

lemeurherve commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

krisstern commented Jan 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lemeurherve commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

krisstern commented Jan 13, 2026

Uh oh!

krisstern commented Jan 14, 2026

Uh oh!

MarkEWaite commented Jan 14, 2026

Uh oh!

krisstern commented Jan 14, 2026

Uh oh!

lemeurherve commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MarkEWaite commented Jan 15, 2026

Uh oh!

krisstern commented Jan 15, 2026

Uh oh!

krisstern commented Jan 15, 2026

Uh oh!

jglick commented Jan 15, 2026

Uh oh!

krisstern commented Jan 15, 2026

Uh oh!

krisstern commented Jan 18, 2026

Uh oh!

MarkEWaite commented Jan 18, 2026

Uh oh!

jonesbusy commented Jan 18, 2026

Uh oh!

MarkEWaite commented Jan 18, 2026

Uh oh!

uhafner commented Jan 18, 2026

Uh oh!

viceice commented Jan 19, 2026

Uh oh!

Reviewers

shalinisudarsan commented Jan 8, 2026 •

edited by krisstern

Loading

lemeurherve commented Jan 8, 2026 •

edited

Loading

lemeurherve commented Jan 8, 2026 •

edited

Loading

lemeurherve commented Jan 8, 2026 •

edited

Loading

MarkEWaite commented Jan 8, 2026 •

edited

Loading

lemeurherve commented Jan 9, 2026 •

edited

Loading

krisstern commented Jan 11, 2026 •

edited

Loading

lemeurherve commented Jan 13, 2026 •

edited

Loading

lemeurherve commented Jan 14, 2026 •

edited

Loading