Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: d27cff8fd2f500162368c265ab4d40808eb444da
https://github.com/jenkinsci/jenkins/commit/d27cff8fd2f500162368c265ab4d40808eb444da
Author: Stephen Connolly <[email protected]>
Date: 2016-02-04 (Thu, 04 Feb 2016)
Changed paths:
M core/src/main/java/hudson/ClassicPluginStrategy.java
Log Message:
-----------
[FIXED JENKINS-32765] Allow the directory that plugins are exploded into to
be changed
- This really has to be controlled by either a system property or a CLI
parameter as we cannot guarantee that any path
specified in a configuration file in JENKINS_HOME will be valid on another
machine where the JENKINS_HOME is mounted
- Obviously Jenkins does not currently support fully starting two Jenkins
instances on the same JENKINS_HOME, so this
fix is to assist in Disaster Recovery (or semi-higher availability)
sceanarios where the backup node is being brought
up. In such cases, the node that failed may not have correctly released all
its file handles in the backing NFS share
and thus could be blocking the recovery node from starting up.
- An additional use case is where the JENKINS_HOME is stored on a remote disk,
e.g. a SAN, etc. and the user wants to
take advantage of the faster local disk to serve the resources from both
plugins and Jenkins core. Without this change
only Jenkins core can be relocated outside of JENKINS_HOME (using the
'--webroot=...' command line option).
- Ideally we would introduce this into the extras-executable-war module once
the system property has had time to soak
(although in an ideal world that module would be agnostic of Jenkins and thus
it might not be appropriate there)
Commit: c0cbff72972d7611da187f6258116e6b60d78e7d
https://github.com/jenkinsci/jenkins/commit/c0cbff72972d7611da187f6258116e6b60d78e7d
Author: Stephen Connolly <[email protected]>
Date: 2016-02-04 (Thu, 04 Feb 2016)
Changed paths:
M core/src/main/java/hudson/ClassicPluginStrategy.java
M core/src/main/java/hudson/PluginManager.java
Log Message:
-----------
[JENKINS-32765] Perhaps it makes more sense to make this a property of the
PluginManager rather than the classic strategy
- Also expose via servlet context parameter of same name to allow multiple
instances of Jenkins in the same servlet container to have different directories
- As we are no longer a constant, change the system property to camelCase
Commit: bdb3c0c6d5e368d3751b3c6dcac8863df217604a
https://github.com/jenkinsci/jenkins/commit/bdb3c0c6d5e368d3751b3c6dcac8863df217604a
Author: Stephen Connolly <[email protected]>
Date: 2016-02-04 (Thu, 04 Feb 2016)
Changed paths:
M core/src/main/java/hudson/PluginManager.java
Log Message:
-----------
[JENKINS-32765] As I am not *adding* a new import, I will annotate with
`@CheckForNull`
Of course the import being used is in a package name that is reserved for
artifacts produced by a JSR... and the JSR that the dependency is claiming to
come from has not actually published anything... thus whoever produced the
artifact has broken the JSR policy... and it is also not safe for us to
actually use these annotations as we do not know what a JSR may change on the
road to actually providing this... but that is a war for a different PR
Commit: 566def3bd6e0d1f9fd8b0cd6f7e9600c95107780
https://github.com/jenkinsci/jenkins/commit/566def3bd6e0d1f9fd8b0cd6f7e9600c95107780
Author: Stephen Connolly <[email protected]>
Date: 2016-02-04 (Thu, 04 Feb 2016)
Changed paths:
M core/src/main/java/hudson/PluginManager.java
Log Message:
-----------
[JENKINS-32765] Fix failing tests
Commit: c11e26504e3936c9ebe8306de5900645a1ab6fa6
https://github.com/jenkinsci/jenkins/commit/c11e26504e3936c9ebe8306de5900645a1ab6fa6
Author: Stephen Connolly <[email protected]>
Date: 2016-02-09 (Tue, 09 Feb 2016)
Changed paths:
M core/src/main/java/hudson/ClassicPluginStrategy.java
M core/src/main/java/hudson/PluginManager.java
Log Message:
-----------
Merge pull request #2012 from stephenc/jenkins-32765
[FIXED JENKINS-32765] Allow the directory that plugins are exploded into to be
changed
Compare:
https://github.com/jenkinsci/jenkins/compare/51f215c3b878...c11e26504e39
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
