Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

Version control capabilities let Bamboo know where the client application for a version control system is located, so that Bamboo can perform a checkout whilst building. Bamboo requires that a capabilitiy for at least one of the following version control repositories to be set so that Bamboo can checkout source code from that repository type:

  • Git (If no capability is provided, Bamboo will use its built-in Git implementation. Note that the built-in Git implementation does not support symbolic links or Git submodules)
  • Mercurial
  • Perforce

Example version control executable paths

For the version control systems that require capabilities to be set on agents, the following table offers example paths for both Linux and Windows systems.

Note that these paths may differ on your actual system's configuration.

Capability typeExample paths
Git
  • /usr/bin/git
  • C:\Program Files\Git\git.exe
Mercurial
  • /usr/local/bin/hg 
  • C:\Program Files\Mercurial\hg.exe
Perforce
  • /usr/bin/p4 
  • c:\Program Files\Perforce Client\p4.exe

To configure a new version control capability:

  1. Navigate to the desired agent, as described in Viewing an agent. 
  2. Select either a local or remote agent.
  3. Choose the version control type you require from Capability Type.

  4. Provide the full path to client executable on the agent machine.

(info) If you install a new agent on a machine that has Git already installed, the agent will find the Git client automatically.

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.