arturobernalg opened a new pull request, #617: URL: https://github.com/apache/jspwiki/pull/617
Every build of master-2.x on Jenkins fails at the first Maven step, for example build #17 of JSPWiki/ci/master-2.x: "MUST USE JDK 17" in the enforcer of jspwiki-builder. The log shows why: the stages clone the repository with `git url: buildRepo`, which checks out the default branch, and the log says "Checking out Revision e5b6fcd... (refs/remotes/origin/master)". So the master-2.x job builds master (JDK 17 and Jakarta) with the JDK 11 stage and stops. The stages now use `checkout scm`, which checks out the branch or the pull request that triggered the build, and the unused buildRepo variable is removed. I cannot run the Jenkinsfile outside Jenkins. What is checked is the cause, from the log above; the build of this pull request on Jenkins is the test of the change. master has the same `git url` lines, so its builds, and the builds of its pull requests, also take the default branch; I have not changed it here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
