You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jenkins#getJnlpJars() API is used to retrieve remoting.jar and jenkins-cli.jar, e.g. SSH Build Agents plugin uses it to install the agent executable on the target host. When Jenkins is packaged with Jenkinsfile Runner, the Jenkins core's logic identifies the source of the Remoting launcher class as JAR and tries to load remoting.jar from a hardcoded WEB-INF/lib/remoting.jar resource. This resource is present in Jenkins WAR packaging, but in JFR the library is located eslewhere. So SSH Build Agents and a few other plugins will fail to retireve the resource
Workaround
Specify a path to WAR by using the -w argument. Full WAR is not required in this directory, just the WEB-INF/lib/remoting.jar file
Full solution
Jenkins core needs to be updated to support custom part to Remoting and Jenkins CLI paths on the filesystem. To do that, a custom system property might be required in the Jenkins core.
The text was updated successfully, but these errors were encountered:
Jenkins#getJnlpJars()
API is used to retrieveremoting.jar
andjenkins-cli.jar
, e.g. SSH Build Agents plugin uses it to install the agent executable on the target host. When Jenkins is packaged with Jenkinsfile Runner, the Jenkins core's logic identifies the source of the Remoting launcher class as JAR and tries to loadremoting.jar
from a hardcodedWEB-INF/lib/remoting.jar
resource. This resource is present in Jenkins WAR packaging, but in JFR the library is located eslewhere. So SSH Build Agents and a few other plugins will fail to retireve the resourceWorkaround
Specify a path to WAR by using the
-w
argument. Full WAR is not required in this directory, just theWEB-INF/lib/remoting.jar
fileFull solution
Jenkins core needs to be updated to support custom part to Remoting and Jenkins CLI paths on the filesystem. To do that, a custom system property might be required in the Jenkins core.
The text was updated successfully, but these errors were encountered: