JGit feature limitations
Our built-in JGit implementation of git is a long-deprecated feature in Bamboo. We are not planning to actively maintain it beyond the security fixes.
We highly recommend installing a compatible native Git client on both Bamboo nodes and remote agents to access all repository-related features in Bamboo, including native Bitbucket DC integration, creation of commits, pushing to the repository, modern SSH key types, and LFS support.
Our Elastic and Ephemeral agents come with the native git already installed and configured.
The following limitations apply:
- The Bamboo JGit feature can only check out repositories.
- It supports both full checkout and a shallow checkout of just the last commit from the specified branch
- The LFS extension is not supported.
- If a repository containing files managed by the LFS extension is checked out, the LFS pointers will not be replaced by the actual files.
- The private keys used for checkout authentication need to be provided in PEM format. Keep in mind the OpenSSH or any other format will not work. Only the following types are accepted:
- DSA (-----BEGIN DSA PRIVATE KEY-----)
- SSH-RSA (-----BEGIN RSA PRIVATE KEY-----)
- ECDSA (-----BEGIN EC PRIVATE KEY-----)
- when linking a Bitbucket Cloud or Github repository, use their respective linked repository types.
- when linking a repository hosted on Bitbucket Data Center or Server and any other source, use the standard Git Repository type.
- An attempt to access the Bitbucket DC or Server repository using the Bitbucket/Stash repository type will fail. The type of key we use to authorize Bamboo with Bitbucket DC using the application links is not supported by our built-in JGit feature.
Last modified on Apr 30, 2024
Powered by Confluence and Scroll Viewport.