|
||||||||
|
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/groups/opt_out.
Could you further clarify your use model?
The code as implemented in git-client-plugin 1.6.2 first checks for git in the default location, then if it is not found there, it will check for an ssh in the same directory as the git executable.
I think that algorithm would support your use model so long as you never install git in the default location. Choosing to never install git in the default location will further support your requirement that every job must explicitly declare its dependencies on the tools it uses.
Is your use case that you want git available in the default location, and you want git in non-default locations, and you want the git executable to be selected first from the path, rather than the current technique which selects ssh first from the default git location, then failing that it selects ssh from the same directory that has the git binary?
Or, is the root problem that the current code is not evaluating the PATH to find the executable.