|
||||||||
|
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 agree with Charles' observation. If the plugin cannot find Git, then it cannot perform its work. You can either configure the location of Git for the slave as needed, or configure the slave, or consider adding "jgit" as a Git implementation on your master configuration, then define the job to use jgit rather than command line git.
The JGit implementation is not as full featured as the command line git implementation, so there are use cases which it does not meet. You could attempt it and see if it meets your needs.