Jenkins build fails with There seems to be a similar issue
https://issues.jenkins-ci.org/browse/JENKINS-18578 The issue is marked as resolved. But we are still having a problem. The log is attached.
Unable to launch SSH Slave since 2.68 when HOME is not writable on Master
Oleg Nenashev is this a remoting issue?
Daniel Beck it is, also a Maven issue (CC Arnaud Héritier).
Just to clarify, the issues happens, because the master acts as an agent in master<=>Maven communications when the Maven build starts. Remoting since 3.7 tries to initialize a default JAR cache and not surprisingly fails when you run the master in a Tomcat container.
It is actually similar to JENKINS-45755, likely a leftover. I will need to verify it manually, but likely picking a default cache in Launcher was a bad idea.
It would be also great to update Maven plugin to use less ancient Remoting APIs
I do not anticipate to get any Remoting maintenance time in foreseeable future, so I have decided to unassign myself from this ticket. Sorry about this regression. It should be a newbie-friendly ticket, and everybody is welcome to contribute.
This will be picked up by a Jenkins weekly build soon.