Azure Linux VMs cannot run jfrog-cli as "jenkins" home directory is "adoptopenjdk"

[andrew-m-leonard]

The jenkins home directory for Azure Linux VMs is /home/adoptopenjdk, instead of /home/jenkins, this results in plugin tools like "jfrog-cli" not being found as the jenkins pipeline searches /home/jenkins/tools which does not exist...?

[andrew-m-leonard]

Temporarily disabled the ci.adoptium.net Azure Cloud Linux-build agent, by changing dockerBuild tag to XdockerBuild
This is to allow the installer job to run successfully on the 1 static dockerBuild node.

[andrew-m-leonard]

The problem is not actually the VM, it's due to the Artifactory installer upload pipeline incorrectly combining "Declarative" and "Scripted" Jenkins pipeline syntax: https://github.com/adoptium/installer/blob/master/linux/Jenkinsfile
As stated in the Jfrog-cli doc: https://jfrog.com/help/r/jfrog-integrations-documentation/use-declarative-or-scripted-syntax-with-pipelines

When working with the Jenkins Artifactory plugin, be sure to choose either scripted or declarative. In other words, do not use declarative and scripted steps within a single pipeline. This will not work.

The jfrog-cli Declarative tools definition sets up the pipeline environment for the agent the top-level pipeline runs on, the pipeline then switches to "scripted" mode and switches context using node(), the jfrog-cli will then not necessarily work in that context.

Raised installer issue: adoptium/installer#1042