|
||||||||
|
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.
Take a guess why I know so well how labels caching works![]()
So, yeah, Jenkins opts for providing access to the massive internal (plugin + Groovy scripts) API – basically everything it has, including the ugly parts – rather than a shiny facade that isn't nearly powerful enough. I think it's generally the right choice, but it comes with issues like this one.
Note that the main problem here may be that using labels for something as dynamic as this looks like the wrong approach (as the caching indicates, they are thought of as fairly static). Check out the extension points modifying queue behavior (e.g. QueueTaskDispatcher), maybe what you're doing would be best implemented in a plugin?