summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Rose <crose@gitlab.com>2018-06-27 16:35:59 +0000
committerChris Rose <crose@gitlab.com>2018-06-27 16:35:59 +0000
commit8c608dad37f52fb30f2a95a22f8f00c82a90550a (patch)
tree2d6c5a9f3430685611a280de244ad4c7df9a6a8e
parentf63e234b57e07e2020f9698f48c9515905d4b6a3 (diff)
downloadgitlab-ce-8c608dad37f52fb30f2a95a22f8f00c82a90550a.tar.gz
Add detail around 'Build Key' within the GitLab steps.
-rw-r--r--doc/user/project/integrations/bamboo.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/user/project/integrations/bamboo.md b/doc/user/project/integrations/bamboo.md
index 1e28646bc97..cffe456cbc2 100644
--- a/doc/user/project/integrations/bamboo.md
+++ b/doc/user/project/integrations/bamboo.md
@@ -41,8 +41,7 @@ service in GitLab.
1. Click 'Atlassian Bamboo CI'
1. Select the 'Active' checkbox.
1. Enter the base URL of your Bamboo server. 'https://bamboo.example.com'
-1. Enter the build key from your Bamboo build plan. Build keys are a short,
- all capital letter, identifier that is unique. It will be something like PR-BLD
+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
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.