-
New Feature
-
Resolution: Fixed
-
Minor
-
None
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)
[JENKINS-32765] Allow the directory that plugins are exploded into to be changed
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/Main.java
http://jenkins-ci.org/commit/extras-executable-war/6fff1412cfc3a0d38a6834475857ace4f9d17969
Log:
JENKINS-32765Expose the exploded plugin archive directory as a command line option