Git client3.3.0Minimum Jenkins requirement: 2.204.1ID: git-client

Installs: 266545
Last released:
Mark Waite
Robert Sandell
Francisco J. Fernández

Build Contributors Jenkins Plugin Installs GitHub release Gitter


Jenkins logo plus Git logo

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.

Changelog in GitHub Releases

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.


The git client plugin also includes two optional implementations that use Eclipse JGit. Eclipse JGit is a pure Java implementation of git. The JGit implementation in the git client plugin provides most of the functionality of the command line git implementation. When the JGit implementation is incomplete, the gap is noted in console logs.

JGit is disabled by default when the git client plugin is installed.

Enabling JGit

Click the "Add Git" button in the "Global Tool Configuration" section under "Manage Jenkins" to add JGit or JGit with Apache HTTP Client as a git implementation.

Enable JGit or JGit with Apache HTTP Client

JGit with Apache HTTP Client

The original JGit implementation inside the git client plugin had issues with active directory authentication. A workaround was implemented to provide JGit but use Apache HTTP client for authentication. The issue in JGit has now been resolved and delivered in git client plugin releases. JGit with Apache HTTP Client continues to delivered to assure compatibility.

Windows Credentials Manager

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.

Bug Reports

Report issues and enhancements with the Jenkins issue tracker.

Contributing to the Plugin

Refer to contributing to the plugin for contribution guidelines.

ArchivesGet past versions

Previous Security Warnings