|
||||||||
|
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/groups/opt_out.
I struggled with this same problem. Selecting the p4 executable name on the configure page of the project that used p4 fixed it for me.
Go into the job that is using p4, select configure, go to the perforce section, select advanced, and select the p4 executable in the p4 executable menu.
Note this was already selected for me since I only had one configured. Select save.
The next build used the full path of the p4 executable that I supplied in the Jenkins->Manage Jenkins->Configure system page.