|
||||||||
|
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.
The git plugin has two alternative implementations. Both implementations are available, so you can choose between them.
The default implementation uses command line git. It assumes you already have git installed and configured on your computer. It is the most feature-rich implementation, but requires that you install and configure git. That is not hard, but it is one more step in the process.
The JGit implementation uses a pure Java implementation of git. It does not require any git installation on your computer. It is not as feature-rich, with several operations (like push, and reference repositories, and shallow clones) not yet implemented. However, it is good at declaring in the console output if you requested something which is not implemented.
The JGit implementation is not visible to jobs until it is added to the global Jenkins configuration. Once it has been added (through http://localhost:8080/configure, for example), then you can select which git implementation you will use on a job by job basis.