Revert "Bump org.jenkins-ci:jenkins from 1.122 to 1.123" #847
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #844
Currently stumped by a JTH release failure. https://github.com/jenkinsci/jenkins-test-harness/actions/runs/11060243118/job/30730386885 complains about missing
org.jenkins-ci.main:jenkins-war:executable-war:2.476
. Indeed https://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/2.476/ only hasjenkins-war-2.476.war
but that is by design; jenkinsci/maven-hpi-plugin#65 + #61 are supposed to look up the*.war
and just add it to the Java classpath. https://github.com/jenkinsci/jenkins-test-harness/actions/runs/10966208526/job/30453668284 worked normally just a few days ago (using the same versions of Maven and Java), and the only POM change since then is #844 which… hmm, https://github.com/jenkinsci/pom/releases/tag/jenkins-1.123 does not mention it but jenkinsci/pom@jenkins-1.122...jenkins-1.123 does show this including jenkinsci/pom#608 with a lot of changes in https://github.com/jenkinsci/maven-hpi-plugin/releases/tag/maven-hpi-plugin-3.58 like jenkinsci/maven-hpi-plugin#649 which might be causing trouble somehow?I failed to reproduce any problem locally with