Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18381

Some node properties do not make sense as global node properties

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 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.

            stephenconnolly Stephen Connolly
            stephenconnolly Stephen Connolly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: