Status: Closed (View Workflow)
For cases where JENKINS_HOME is located on e.g. NFS or a SAN, as the exploded plugin directories are really a redundant copy, it would be beneficial to be able to relocate these outside of JENKINS_HOME (much like the --webroot parameter allows relocating the extracted WAR file directory outside of JENKINS_HOME)
Most likely the only way to implement this is as either a system property or a CLI parameter as by the time Jenkins has started up it is too late to change the configuration option.
Additionally there is the use case where the JENKINS_HOME is on a redundant file system in case of disaster recovery, so the target extraction directory may vary depending on which node in the DR is being brought on-line, so it does not make sense to store this in a configuration file (as there is no guarantee that the mount paths are the same, etc)
Integrated in jenkins_main_trunk #4449
JENKINS-32765 Update extras-executable-war to pick up system property (Revision 20317bb1e409d30626abf43f88bee07aa29524f3)
Result = SUCCESS
stephen connolly : 20317bb1e409d30626abf43f88bee07aa29524f3
Wouldn't it make more sense to introduce a single parameter "--cacheroot" (or something like that) where the webroot, the pluginroot and also the jar cache could be put (see
JENKINS-18578), instead of providing an extra parameter for all of these?
That wouldn't work for people running in Bring-Your-Own-Servlet-Container mode, those people need a separate configurable option as the webapp expansion is controlled by e.g. Tomcat.
Additionally, when testing multiple versions of Jenkins it can be helpful to use different -
webroot options with the same -pluginroot (assuming you have done the correct pinning)
Code changed in jenkins
User: Stephen Connolly
JENKINS-32765Update extras-executable-war to pick up system property and record feature in changelog