Backporting for 2.426.1

[MarkEWaite]

Backporting for LTS 2.426.1

Latest core version: Jenkins 2.429

Fixed

JENKINS-72248           Minor                   2.428
        Backport uptime telemetry
        https://issues.jenkins.io/browse/JENKINS-72248

JENKINS-72189           Major                   2.430
        Drag&Drop for repeatables not working for existing entries (regression in 2.335)
        regression
        https://issues.jenkins.io/browse/JENKINS-72189

JENKINS-72179           Minor                   2.429
        Parameters view of builds does not show descriptions of checkbox parameters (regression in 2.179)
        regression
        https://issues.jenkins.io/browse/JENKINS-72179

JENKINS-72170           Major                   2.428
        Cannot add additional branch sources in multibranch pipeline after 2.422
        regression
        https://issues.jenkins.io/browse/JENKINS-72170

JENKINS-72163           Major                   3160.vd76b_9ddd10cc
        Retry on initial connection failure occurs in one entrypoint but not the other
        https://issues.jenkins.io/browse/JENKINS-72163

JENKINS-72156           Minor                   2.428, 2.414.3
        Include Jetty 10.0.17 in a Jenkins release
        https://issues.jenkins.io/browse/JENKINS-72156

JENKINS-72020           Minor                   2.428
        Unable to reorder clouds anymore via UI
        https://issues.jenkins.io/browse/JENKINS-72020

JENKINS-71937           Major                   2.427
        Jenkins 2.421 breaks vSphere Cloud agent labels
        regression
        https://issues.jenkins.io/browse/JENKINS-71937

JENKINS-71252           Critical                2.427
        Form validation is never displayed for fields initially hidden under Advanced section (regression in 2.355)
        regression
        https://issues.jenkins.io/browse/JENKINS-71252

JENKINS-70793           Minor                   2.427
        Form validation does not clear previous errors (regression in 2.355)
        regression
        https://issues.jenkins.io/browse/JENKINS-70793

JENKINS-65368           Major                   3159.vb_8c0ef2b_55a_f as included in 2.428
        Remoting agent.jar does not work behind proxy
        https://issues.jenkins.io/browse/JENKINS-65368

The developer mailing list has the backporting announcement. The 2.426.1 release checklist has more information as well.

Several candidates are not included in this pull request, but the authors of those candidates have been asked if those changes should be included in the 2.426.1 LTS backports. Those include:

• Fix drag and drop for repeatables - JENKINS-72189 & JENKINS-71089

Testing done

Ran the generated war file interactively with Java 11, Java 17, and Java 21 and confirmed that it was well behaved with a few minutes of interactive testing.

Ran tests successfully with mvn clean verify on Linux.

Proposed changelog entries

N/A - changelog will be created by the documentation team.

Proposed upgrade guidelines

N/A - no items in this pull request that need an entry in the upgrade guide

Submitter checklist

• The Jira issue, if it exists, is well-described.
• 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.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@NotMyFault

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

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• 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).
• 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).

[MarkEWaite]

Based on the answer from @timja I've added e6b453b , a backport of the fix for JENKINS-72020 - Restore ability to reorder clouds

[MarkEWaite]

@daniel-beck replied and marked two issues as LTS candidates so they are included as 5080643 and b560797

Those are backports of:

• Add telemetry for Jenkins uptime #8596
• [JENKINS-72179] Show description of boolean build parameter values #8606

[jglick]

FTR jenkinsci/remoting@3148.v532a_7e715ee3...3160.vd76b_9ddd10cc = jenkinsci/remoting#675 plus some unrelated changes; see discussion in https://issues.jenkins.io/browse/JENKINS-72163

[MarkEWaite]

Thanks for pointing to that difference! I had missed that there is an additional bug fix that is included in remoting 3160 as delivered in Jenkins 2.428. The additional fix is JENKINS-65368 Remoting agent.jar does not work behind proxy. I've labeled that bug report as 2.426.1-fixed in Jira and included it in the pull request description