Backporting for LTS 2.440.2

[krisstern]

Latest core version: jenkins-2.448

Postponed
---------

JENKINS-72799           Minor                   Tue, 5 Mar 2024 13:24:45 +0000
        ConsoleLogFilter is not applied to all SlaveComputer logging
        https://issues.jenkins.io/browse/JENKINS-72799

Fixed
-----

JENKINS-72775           Minor                   2.444
        Update Winstone to 6.18 to get Jetty 10.0.20
        https://issues.jenkins.io/browse/JENKINS-72775

JENKINS-72711           Minor                   2.446
        Build History page no longer uses animated icons for builds in progress (regression in 2.434)
        regression
        https://issues.jenkins.io/browse/JENKINS-72711

JENKINS-72407           Major                   <a href="https://www.jenkins.io/changelog/?query#v2.443">https://www.jenkins.io/changelog/?query#v2.443</a>
        Build status icon missing for multibranch pipeline
        https://issues.jenkins.io/browse/JENKINS-72407

JENKINS-71148           Trivial                 2.447
        Do not display empty tooltips
        https://issues.jenkins.io/browse/JENKINS-71148

Submitter checklist

Preview 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.

Desired reviewers

N/A

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

Maintainer checklist

Preview 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).

[kmartens27]

@krisstern can you confirm whether

 JENKINS-72407           Major                   <a href="https://www.jenkins.io/changelog/?query#v2.443">https://www.jenkins.io/changelog/?query#v2.443</a>
        Build status icon missing for multibranch pipeline
        https://issues.jenkins.io/browse/JENKINS-72407

is the same as what's mentioned in the 2.440.1 backporting? I ask because the empty folder icons were included in the last LTS changelog.

I just want to make sure that it is included in the correct changelog, so if it did not get released as part of .1, then I need to adjust everything accordingly.

[krisstern]

@kmartens27 Yes, the commit referring to in

JENKINS-72407           Major                   <a href="https://www.jenkins.io/changelog/?query#v2.443">https://www.jenkins.io/changelog/?query#v2.443</a>
        Build status icon missing for multibranch pipeline
        https://issues.jenkins.io/browse/JENKINS-72407

is an empty commit. Should be okay codewise. However, I am not sure if this is needed. I am including this resolved commit again for completeness' sake, so that we can close the JIRA issue for it.

[basil]

The fix for JENKINS-72407 was already backported to stable-2.440 in #8945. I do not see a need for an empty commit, as this feels like process for its own sake rather than for the sake of achieving any specific goal. But I do not feel strongly either way.

[daniel-beck]

I changed the Jira labels from 2.440.2-fixed to 2.440.1-fixed to reflect reality. CC @NotMyFault who switched it back from 2.440.1-fixed to lts-candidate in case I'm missing something.

[krisstern]

I have removed the commit for:

JENKINS-72407           Major                   <a href="https://www.jenkins.io/changelog/?query#v2.443">https://www.jenkins.io/changelog/?query#v2.443</a>
        Build status icon missing for multibranch pipeline
        https://issues.jenkins.io/browse/JENKINS-72407