I have a build template setup where the user can choose the JDK tool in a parameter to the build. No matter what they choose to build this Java-source project with, the default JAVA_HOME setup in the Jenkin's user's shell environment is used, seemingly regardless of what tool is selected in the job's execution.

I have three Java JDK tools defined in Jenkins configuration's Tools Locations, and the job's parameters show all three as available, but regardless of what's selected, the default JDK used is the JAVA_HOME defined in the Jenkin's user's $HOME environment.

I am also seeing the "No JDK (JDK x.y.z) found" issue that seems to have resurfaced again.