-
New Feature
-
Resolution: Fixed
-
Minor
-
None
Since 1.472+ it has been possible to configure the master node's own properties.
There are some node properties that do not make sense as a global node property. Up until Jenkins 1.472 the way to mark properties as such was to return false from NodePropertyDescriptor.isApplicable(clazz) if clazz instanceof Jenkins
That technique no longer works as that also means that the property cannot be configured as a node property of the master directly.
There needs to be an alternative mechanism for differentiating properties that can be applied to all nodes from properties that can be applied to the master node.
Code changed in jenkins
User: Stephen Connolly
Path:
changelog.html
core/src/main/java/hudson/Functions.java
core/src/main/java/hudson/slaves/NodePropertyDescriptor.java
core/src/main/resources/jenkins/model/GlobalNodePropertiesConfiguration/config.groovy
http://jenkins-ci.org/commit/jenkins/48e801023123f84ee4eebf60737089f41b44958e
Log:
JENKINS-18381Provide a mechanism to differentiate between nodeproperties that are applicable to the master node only and node properties
that can be applied to all nodes