Update dependency org.jenkins-ci.main:jenkins-war to v2.535

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
org.jenkins-ci.main:jenkins-war	2.533 -> 2.535

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[timja]

Input step likely caused by jenkinsci/jenkins#11177 (comment)

Azure SDK is an ACP timeout

Workflow-CPS is jenkinsci/jenkins#11208 (comment)

[janfaracik]

Opened jenkinsci/workflow-cps-plugin#1104

[jglick]

https://github.com/jenkinsci/workflow-cps-plugin/releases/tag/4218.vff679a_5c0f3a_ ICYMI

[jglick]

#5920

[jglick]

@alecharp use the update checkbox, not the GH update branch button

[alecharp]

gitlab-plugin test failure is due to the update of parent pom in sample-plugin. It is reproducible in gitlab-plugin directly by updating the parent pom there. Further research is required (I'm on it) to see what in the parent pom creates this problem.

I haven't diagnosed the durable-task nor pipeline-input-step plugins failures.

[jglick]

jenkinsci/gitlab-branch-source-plugin#514 (comment) ICYMI @alecharp nm, different plugin

[jglick]

InputStepTest failures should have been resolved by #5920, not sure why they were not; CC @das7pad

[jglick]

durable-task failures were probably caused by jenkinsci/durable-task-plugin#274, CC @strangelookingnerd

[strangelookingnerd]

durable-task failures were probably caused by jenkinsci/durable-task-plugin#274, CC @strangelookingnerd

Seems that the checks for the Docker environment are now executed too late to skip the tests. Is jenkinsci/durable-task-plugin#301 going to address this?

[jglick]

Regarding #5906 (comment), after dealing with jenkins-infra/helpdesk#4669 (comment)

PLUGINS=pipeline-input-step bash local-test.sh

passes for me as of a7c6510. Perhaps the core changes made the test flaky?

[das7pad]

InputStepTest failures should have been resolved by #5920, not sure why they were not; CC @das7pad

In the build logs I see

https://ci.jenkins.io/job/Tools/job/bom/job/PR-5906/6/pipeline-overview/?start-byte=0&selected-node=12906#log-12906-22
PCT_D_ARGS+='-Djenkins-test-harness.version=2516.vc8fe6b_362b_19 '.

The htmlunit fix was first included in 2519:

• jenkinsci/jenkins-test-harness@4ee63f8
• https://github.com/jenkinsci/jenkins-test-harness/releases/tag/2519.v4ee63f85da_71
• Bump org.jenkins-ci.main:jenkins-test-harness-htmlunit from 221.vfef8db_a_a_a_57e to 225.v7d540e18a_8f4 jenkins-test-harness#1045

[jglick]

Ah #4689 thus waiting for #5931