Backporting for LTS 2.541.2 started

[Shalini Sudarsan]

Hey everyone,

Backporting for 2.541.2 has started, and the RC is scheduled for 2026-02-04.

Candidates: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3Alts-candidate
Fixed: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3A2.541.2-fixed
Rejected: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3A2.541.2-rejected

Best regards,

Shalini Sudarsan

[Jan Meiswinkel]

I see that https://github.com/jenkinsci/jenkins/issues/26254 is a backport candidate still. Has there been a decision on it? Would be great if it could get backported for this particular LTS as it can really slow down the Jenkins controller.

[Mark Waite]

On Mon, Feb 16, 2026 at 3:06 AM Jan Meiswinkel wrote:

I see that https://github.com/jenkinsci/jenkins/issues/26254 is a backport candidate still. Has there been a decision on it? Would be great if it could get backported for this particular LTS as it can really slow down the Jenkins controller.

Not included in 2.541.2.  It was first released in Jenkins weekly 2.550 last week.  It will be reviewed for inclusion in the next LTS.

 

shall...@gmail.com schrieb am Donnerstag, 29. Januar 2026 um 02:42:05 UTC+1:

Hey everyone,

Backporting for 2.541.2 has started, and the RC is scheduled for 2026-02-04.

Candidates: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3Alts-candidate
Fixed: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3A2.541.2-fixed
Rejected: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aclosed%20label%3A2.541.2-rejected

Best regards,

Shalini Sudarsan

--
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 visit https://groups.google.com/d/msgid/jenkinsci-dev/bb5e05f3-1f3a-4b12-8a2a-2dae904ea796n%40googlegroups.com.

[Daniel Beck]

On Mon, Feb 16, 2026 at 3:06 AM Jan Meiswinkel wrote:

I see that https://github.com/jenkinsci/jenkins/issues/26254 is a backport candidate still. Has there been a decision on it? Would be great if it could get backported for this particular LTS as it can really slow down the Jenkins controller.

If you want a change backported, the best time to advocate for that is well before the release date. In this case, the only plugin for which this issue was reported (that I'm aware of at least, and I haven't checked all other uses of the new core APIs yet) has been changed so the issue doesn't occur, so there was no reason for us to consider expediting this backport. Given 2.550 was released after the LTS RC was prepared, it follows from the documentation at https://www.jenkins.io/download/lts/ that this issue is not usually considered a candidate yet.

There are also no related discussions in the forum or users mailing list that I can find. I expect there's a relatively straightforward workaround via script console/init script that would even allow you to enforce CSP if you want. If you decide to go that route, please ping/cc me in the thread you open.

CONFIDENTIALITY NOTICE: This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email.