2017-02-03 13:41:35 -05:00
# Atlassian Bamboo CI Service
GitLab provides integration with Atlassian Bamboo for continuous integration.
When configured, pushes to a project will trigger a build in Bamboo automatically.
Merge requests will also display CI 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.
## Setup
2017-02-07 16:20:36 -05:00
### Complete these steps in Bamboo
2017-02-03 13:41:35 -05:00
1. Navigate to a Bamboo build plan and choose 'Configure plan' from the 'Actions'
2017-02-07 16:20:36 -05:00
dropdown.
2017-02-03 13:41:35 -05:00
1. Select the 'Triggers' tab.
1. Click 'Add trigger'.
1. Enter a description such as 'GitLab trigger'
1. Choose 'Repository triggers the build when changes are committed'
1. Check one or more repositories checkboxes
2017-02-07 16:20:36 -05:00
1. Enter the GitLab IP address in the 'Trigger IP addresses' box. This is a
whitelist of IP addresses that are allowed to trigger Bamboo builds.
2017-02-03 13:41:35 -05:00
1. Save the trigger.
2017-02-07 16:20:36 -05:00
1. 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.
2017-02-03 13:41:35 -05:00
1. Select the 'Miscellaneous' tab.
2017-02-07 16:20:36 -05:00
1. Under 'Pattern Match Labelling' put '${bamboo.repository.revision.number}'
in the 'Labels' box.
2017-02-03 13:41:35 -05:00
1. Save
Bamboo is now ready to accept triggers from GitLab. Next, set up the Bamboo
2017-02-07 16:20:36 -05:00
service in GitLab.
2017-02-03 13:41:35 -05:00
2017-02-07 16:20:36 -05:00
### Complete these steps in GitLab
2017-02-03 13:41:35 -05:00
1. Navigate to the project you want to configure to trigger builds.
2017-02-07 16:20:36 -05:00
1. Navigate to the [Integrations page ](project_services.md#accessing-the-project-services )
2017-02-03 13:41:35 -05:00
1. Click 'Atlassian Bamboo CI'
1. Select the 'Active' checkbox.
1. Enter the base URL of your Bamboo server. 'https://bamboo.example.com'
2018-06-27 12:35:59 -04:00
1. 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 seperated with a '-' for example **PROJ-PLAN** . This is a short, all capital letter, identifier that is unique. When viewing a plan within Bamboo, the build key is also shown in the browser URL for example https://bamboo.example.com/browse/PROJ-PLAN
2017-02-07 16:20:36 -05:00
1. 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.
2017-02-03 13:41:35 -05:00
1. Save or optionally click 'Test Settings'. Please note that 'Test Settings'
2017-02-07 16:20:36 -05:00
will actually trigger a build in Bamboo.
2017-02-03 13:41:35 -05:00
## Troubleshooting
2017-04-11 08:11:49 -04:00
If builds are not triggered, ensure you entered the right GitLab IP address in
Bamboo under 'Trigger IP addresses'.
>**Note:**
- Starting with GitLab 8.14.0, builds are triggered on push events.
2017-02-03 13:41:35 -05:00