|
||||||||
|
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.
It works when I pin it to a single node via the "Restrict where this project can be run" job configuration. It still does not work when using the Node Parameter Plugin for a single node either.
Unfortunately, we do not have the resources available to set up a new Jenkins instance to test this. Based on the other comments, this is easy to reproduce for anyone who wants to attempt to fix it.
Added information. This is only a problem for my two Windows slave nodes. I have the same configuration for several Linux nodes and it is able to find the 'sh' command without issue. This matches the first comment of this defect.