|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
jenkins.model.Jenkins.trimLabels() documents this specific issue (Label.reset() does not, presumably because it's non-public). The problem is that, even if it's so accessible through the use of plugins, you are programming Jenkins using its internal API. So you cannot disregard internal structures or their constraints.
Additionally, you're way beyond what would usually be possible to do with labels – so it's not unreasonable that your use case is not covered by Jenkins internals without some additional work and understanding on your part.
If Jenkins wouldn't update effective labels after submitting the slave node config form, it'd be different.