remoteFs should be automatically created by agents on-demand. Robert has pointed to the right part of the code.
However, there are some tricky bits with that...
- Jenkins agent is able to connect and ACCEPT RUNS even if RemoteFs is not writable
- The runs will obviously fail, but it won't prevent Jenkins from scheduling new Jobs to there
In order to fix this problem, in Remoting 3.8 I have introduced support of
Work Directories. If an agent starts with with the "-workDir" flag, it will check write-ability of the work directory (which is equal to remoteFS for Java Web Start launchers) and fail if the directory is not writable.
In order to enable such behavior, EC2 plugin just needs to pass the "-workDir" flag when the Remoting version supports it (Jenkins 2.68+).
BR, Oleg
четверг, 30 ноября 2017 г., 15:41:30 UTC+3 пользователь Robert Sandell написал: