The git client plugin provides git application programming interfaces (APIs) for Jenkins plugins. It can fetch, checkout, branch, list, merge, and tag repositories. Refer to the API documentation for specific API details.

The GitClient interface provides the primary entry points for git access. It supports username / password credentials and private key credentials using the Jenkins credentials plugin.

• Introduction
• Changelog in GitHub Releases
• Implementations
  • JGit
  • Enabling JGit
  • JGit with Apache HTTP Client
• Windows Credentials Manager
• Bug Reports
• Contributing to the Plugin

Release notes are recorded in GitHub beginning with git client plugin 2.8.1. Prior release notes are recorded in the git client plugin repository change log.

The git client plugin default implementation requires that command line git is installed on the master and on every agent that will use git. Command line git implementations working with large files should also install git LFS. The command line git implementation is the canonical implementation of the git interfaces provided by the git client plugin.

Command line git is enabled by default when the git client plugin is installed.

Git for Windows is able to integrate with the Windows Credentials Manager for secure storage of credentials. Windows Credentials Manager works very well for interactive users on the Windows desktop. Windows Credentials Manager does not work as well for batch processing in the git client plugin. It is best to disable Windows Credentials Manager when installing Git on Jenkins agents running Windows.

Report issues and enhancements with the Jenkins issue tracker.

Refer to contributing to the plugin for contribution guidelines.