|
||||||||
|
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.
I would not change the definition of getTiedJobs, as that could be considered a regression for others using it.
Simple string matching also will not work, consider the labels windows and windows-server: jobs with the latter will show up for the former which is inconsistent with how labels work.
Note also e.g. negation operators (!windows) that would make no sense for jobs to show up on the windows node page as "tied". Or what about windows||!windows?
A more informative "This label is used by:" is needed (e.g. group jobs by label containing the current LabelAtom) and could be provided as an Action for Labels so it shows up on a separate page.
This is why I suggest this could (and probably should, for now) be provided by a plugin. If it proves useful (and does not result in e.g. performance regressions), this functionality could also be integrated into core in some way later, using essentially the same code.