|
||||||||
|
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'm not persuaded that the change of the plugin from 2.2.5 back to 2.2.4 actually had anything to do with the "fix". I'm not aware of anything in the git plugin changes from 2.2.4 to 2.2.5 which would alter the value of a PATH environment variable and its impact on the PATH passed to a command line git invocation.
I don't intend to investigate this any further, and I think at the moment I'm the primary person tracking git and git client plugin bug reports.
Whether you choose to reopen it or not, my behavior will be the same, I'll ignore this bug report. I assume that eventually I'll return to it and close it completely as either "not a bug" or "cannot reproduce".