Configuring source code management triggers for Subversion

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This page provides instructions on how to configure Subversion to send message events that trigger the execution of Bamboo plans. You only need to configure Subversion to send these message events if The repository triggers the build when changes are committed build strategy has been specified for one or more of your Bamboo plans.

Configuring Subversion to trigger a build

This section explains how to configure Subversion to trigger a build when the repository is changed. A Subversion hook script is used to perform the trigger action whenever a Subversion repository is changed.

The following commands and script files assume that your Subversion server runs on a UNIX- or Linux-based operating system. If your Subversion server runs on any other operating system, then you will need to modify the script files and if necessary, the commands below to suit that operating system.

On this page:

Related pages:

Step 1. Enable the Subversion post-commit hook

To do this, run the following commands:

cd svn-repository-containing-the-build-source-code
cd into the hooks/ directory

The Subversion post-commit file is not installed by default. If it does not exist, make a copy of the post-commit.tmpl file in the hooks/ directory, name it post-commit and make it executable:

cp post-commit.tmpl post-commit
chmod a+rx post-commit

Step 2. Install the post-commit trigger

Add a line like the following to the post-commit file, for running Bamboo's build trigger script file.

/path-to-your-bamboo-installation/scripts/svn-triggers/ base-url BUILD-KEY


  • base-url is the base URL of the Bamboo server. For example:

  • BUILD-KEY is the key of the Bamboo plan to be executed.

Make Bamboo's build trigger script file executable (using chmod) so that the Subversion user can execute it.

Step 3. Do a test commit

Conduct a 'test' commit. Bamboo should start building the relevant plan after a few seconds.

The Bamboo log file should contain an entry like this:

[INFO] - Bamboo build was triggered by remote http call from


Build Trigger Security — Bamboo will only accept remote build triggers if the triggers originated from the Subversion server(s) identified in the Subversion Repository URL of any Bamboo plans. Requests originating from other Subversion servers will be rejected by Bamboo.

Last modified on Oct 9, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.