|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
The "usage" setting is also affected.
The reason is that Jenkins is not consistent with regards to labels & usage setting for the master node in the Configure System page and in the master node Configure page.
In the first case the settings are controlled by a condition (!app.slaves.isEmpty() || !app.clouds.isEmpty()), in the other case they are not.
I think the simplest way to solve this is to remove the condition from MasterBuildConfiguration/config.grovvy. At worse it doesn't harm anything since these settings are accessible via another page, and at best it solves the problem described here (which by the way was very annoying when I was working on the Label Link Jobs plugin).
Note that the !app.clouds.isEmpty() was introduced to solve JENKINS-11100. Removing the condition altogether would not make a difference for this resolution.