In INFRA-1633 R. Tyler Croy pointed to this announcement about this system, so I tried it out on an obscure plugin. That failed:
Unpacking https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip to /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn on aci-maven-s1s9x
[jdk8] $ tar xzf /home/jenkins/tools/hudson.model.JDK/jdk8/jdk.sh
mvn --batch-mode --show-version --errors '-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn' -s /home/jenkins/workspace/Plugins_log-cli-plugin_PR-13@tmp/settings-azure.xml --update-snapshots '-Dmaven.repo.local=/home/jenkins/workspace/Plugins_log-cli-plugin_PR-13@tmp/m2repo' -Dmaven.test.failure.ignore clean install
/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn/bin/mvn: exec: line 191: /home/jenkins/tools/hudson.model.JDK/jdk8/bin/java: not found
ERROR: script returned exit code 127
Perhaps there was nothing wrong with the image or agent per se, but buildPlugin was still attempting to install the JDK and Maven from tools, and besides being wasteful this does not work for some reason which is not clear from the log.
I suppose buildPlugin could suppress the tool step usage when it finds the maven or maven-11 "platforms" being selected?