Backporting for LTS 2.452.2

[krisstern]

Latest core version: jenkins-2.459

Postponed
---------

JENKINS-73168           Minor                   2.459
        "No changes" does not appear (regression in 2.453)
        regression
        https://issues.jenkins.io/browse/JENKINS-73168

Fixed
-----

JENKINS-73114           Minor                   2.459
        Jenkins css classes for alerts collide with bootstrap5
        https://issues.jenkins.io/browse/JENKINS-73114

JENKINS-73093           Minor                   2.457
        Update bundled script-security to 1336.vf33a_a_9863911
        https://issues.jenkins.io/browse/JENKINS-73093

JENKINS-72622           Major                   2.459
        EC2 plugin cannot add a new cloud
        https://issues.jenkins.io/browse/JENKINS-72622

JENKINS-64553           Major                   Tue, 28 May 2024 12:59:30 +0000
        ItemListener.onUpdated() isn't fired when modifying Item
        https://issues.jenkins.io/browse/JENKINS-64553

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[daniel-beck]

JENKINS-73114 is a bad backport, see JENKINS-73301.

[jonesbusy]

Any reason JENKINS-64553 is not part of release note ? https://www.jenkins.io/changelog-stable/#v2.452.2

I'm asking because I'm still facing this bug when updating an organization folder via JobDSL (So not sure if it's a backport issue on 2.452.2 or because there are still issue with update event)

Thanks!

[MarkEWaite]

Any reason JENKINS-64553 is not part of release note ? https://www.jenkins.io/changelog-stable/#v2.452.2

I'm asking because I'm still facing this bug when updating an organization folder via JobDSL (So not sure if it's a backport issue on 2.452.2 or because there are still issue with update event)

Thanks!

Thanks for catching that mistake.

The change was backported in:

• https://github.com/jenkinsci/jenkins/pull/9305/commits

It is the first commit in the 2.452.2 backport pull request with SHA d87e891

It was missed when creating the changelog and when reviewing the changelog. I've added it to the changelog as:

• Add JENKINS-64553 fix ItemListener to 2.452.2 changelog jenkins-infra/jenkins.io#7374