|
||||||||
|
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.
Hey Daniel,
I'm realizing now that I should have set it as a "core" issue instead of a groovy-plugin one, my mistake on that. I still believe that this is a Jenkins issue however as Jenkins core is not acting as expected. I would never expect Jenkins to run a job on a node that is not suited for that job through the assigned labels. Cached or not, Jenkins should still run a sanity check on its jobs before running them.