Atlassian Bamboo Service

GitLab provides integration with Atlassian Bamboo for continuous integration. When configured, pushes to a project trigger a build in Bamboo automatically. Merge requests also display CI/CD status showing whether the build is pending, failed, or completed successfully. It also provides a link to the Bamboo build page for more information.

Bamboo doesn’t quite provide the same features as a traditional build system when it comes to accepting webhooks and commit data. There are a few things that need to be configured in a Bamboo build plan before GitLab can integrate.


Complete these steps in Bamboo

  1. Navigate to a Bamboo build plan and choose Configure plan from the Actions dropdown.
  2. Select the Triggers tab.
  3. Click Add trigger.
  4. Enter a description such as GitLab trigger.
  5. Choose Repository triggers the build when changes are committed.
  6. Select the checkbox for one or more repositories.
  7. Enter the GitLab IP address in the Trigger IP addresses box. This is a list of IP addresses that are allowed to trigger Bamboo builds.
  8. Save the trigger.
  9. In the left pane, select a build stage. If you have multiple build stages you want to select the last stage that contains the Git checkout task.
  10. Select the Miscellaneous tab.
  11. Under Pattern Match Labeling put ${bamboo.repository.revision.number} in the Labels box.
  12. Save

Bamboo is now ready to accept triggers from GitLab. Next, set up the Bamboo service in GitLab.

Complete these steps in GitLab

  1. Navigate to the project you want to configure to trigger builds.
  2. Navigate to the Integrations page
  3. Click Atlassian Bamboo.
  4. Ensure that the Active toggle is enabled.
  5. Enter the base URL of your Bamboo server.
  6. Enter the build key from your Bamboo build plan. Build keys are typically made up from the Project Key and Plan Key that are set on project/plan creation and separated with a dash (-), for example PROJ-PLAN. This is a short, all uppercase identifier that is unique. When viewing a plan in Bamboo, the build key is also shown in the browser URL, for example
  7. If necessary, enter username and password for a Bamboo user that has access to trigger the build plan. Leave these fields blank if you do not require authentication.
  8. Save or optionally click Test Settings. Please note that Test Settings actually triggers a build in Bamboo.


Builds not triggered

If builds are not triggered, ensure you entered the right GitLab IP address in Bamboo under Trigger IP addresses. Also check service hook logs for request failures.

Advanced Atlassian Bamboo features not available in GitLab UI

Advanced Atlassian Bamboo features are not compatible with GitLab. These features include, but are not limited to, the ability to watch the build logs from the GitLab UI.