|
||||||||
|
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.
Although I really understand what Richard is saying, I think using a java implementation for for git has many advantages (as it has for subversion). The administrator not having to setup git on every single slave is just one of the best advantages. An other one is the short commings of the CLI version when it comes to use multiple users for different checkouts on the same slave - in other words security.
But any way as so many users are affected by this issues and as the current version already provides a flag to switch back to the CLI version, I think we should just make that flag more easily configurable in the UI and probably change the default back to the CLI version.
Maybe this could even be done with a "Git Installation" in the System Configuration and have a provided version (Java) in the dropdown as a selection. This way a admin would be able to choose whether version he wants to use per job and not per Jenkins installation.