Bamboo

Bamboo integration connects Bamboo plans with Allure TestOps via a dedicated Bamboo plugin:

• one job in TestOps corresponds to one Bamboo plan;
• one launch corresponds to one Bamboo build (a sequence of Bamboo jobs).

A build can be triggered by either TestOps or Bamboo, with both sides showing its status.

During test execution, the plugin scans the results directory for new files and uploads each file to TestOps as soon as it appears. TestOps can show partial launch results before the build finishes.

The Bamboo plugin does not support TestOps installations with self-signed certificates. Make sure TestOps uses a properly signed certificate, or make it available to Bamboo over plain HTTP before setting up the integration.

Before you begin

• Permission to install or manage Bamboo apps.
• The URL of your TestOps instance and the numeric project ID.
• A TestOps API token for the upload path.
• A Bamboo account for the trigger path from TestOps.

1. Install the Bamboo plugin

1. In Bamboo, click the gear icon in the top right corner and select Manage apps.
2. Click Find new apps.
3. Search for Allure TestOps for Bamboo.
4. Click Install next to the plugin.
5. In the dialog, click Install, then Accept & install. Wait until the plugin is downloaded and enabled.

2. Send results from Bamboo to TestOps

Create the TestOps token

1. In Allure TestOps, click your avatar and open API Tokens.
2. Click + Token.
3. Enter a name for the token, for example Token for Bamboo, and click Create.
4. Copy the generated token.

Configure the Bamboo plan

1. On the Bamboo dashboard, open your build plan.
2. Click Actions → Configure plan.
3. Go to the Other tab.
4. Under Allure Upload, fill in the fields:
   • Enable Allure Upload — checked.
   • Server endpoint url — the URL of the TestOps instance, for example https://testops.example.com.
   • Server token — the API token from the previous step.
   • Project id — the numeric ID of the TestOps project.
   • Launch name — a template for naming launches. You can use Bamboo variables here.
   • Launch tags — comma-separated tags to assign to the launch.
5. Click Save.

Set the results directory on the Bamboo job

1. Open the same plan and click Actions → Configure plan.
2. Click the job that runs the tests.
3. Go to the Other tab.
4. In Test Results Directories, enter the path to the Allure results directory, for example build/allure-results. For multiple directories, separate them with commas or use a wildcard pattern, for example modules/*/build/allure-results.
5. Click Save.

3. Let TestOps trigger Bamboo builds

Add the global Bamboo integration

An instance administrator should:

1. Open Administration → Integrations.
2. Click + Add integration.
3. Select Bamboo CI Server.
4. Fill in the fields:
   • Name — a recognizable name, for example Bamboo production.
   • Endpoint — the URL of the Bamboo instance, for example https://bamboo.example.com/.
5. If Bamboo uses a self-signed SSL certificate, check Disable certificate validation.
6. Click Add integration.

Add Bamboo credentials to the TestOps project

1. In TestOps, open the target project and go to Settings → Integrations.
2. Under Available integrations, find the Bamboo integration and click Add integration.
3. Enter the Username and Password of the Bamboo account.
4. Click Test connection. A "Connection established" message confirms the credentials are correct.
5. Click Add integration.

Configure the Bamboo-backed job in TestOps

The recommended way is to run the Bamboo plan once — after the first successful upload TestOps creates the job automatically:

1. Open Jobs in the TestOps project.
2. Click ⋯ next to the job and select Configure.
3. Fill in the fields:
   • Build server — the global Bamboo integration added by the administrator.
   • Job can be used to run tests — enable to allow triggering from TestOps.
4. Click Submit.

Enable test plan support in the Bamboo job

To allow TestOps-triggered selective execution, add the following environment variable to the Bamboo task that runs the tests:

ALLURE_TESTPLAN_PATH=${bamboo.ALLURE_TESTPLAN_PATH}

1. On the Bamboo dashboard, open the build plan and click Actions → Configure plan.

2. Click the job that runs the tests.

3. In the job's task list, select the task that runs the tests.

4. In the Environment variables field, add ALLURE_TESTPLAN_PATH=${bamboo.ALLURE_TESTPLAN_PATH}.

   

5. Click Save.

4. Pass parameters and branch values

Bamboo uses variables for passing parameters to builds. TestOps integrates this with its Environment concept.

Set the same default values in both TestOps and Bamboo. This ensures a Bamboo build gets the same environment regardless of what triggered it.

Add global environment names

An instance administrator should:

1. Open Administration → Environment.

2. For each parameter, click + Create, enter the name, and click Submit.

   

Map parameters in the project

1. In the project, open Settings → Environment.

2. For each parameter, click + Create (or the edit icon if it already exists):

   • Mapping key — the Bamboo variable name.
   • Environment variable — the global parameter name created by the administrator.

3. Click Submit.

   

Add parameters to the job

1. Open Jobs, click ⋯ next to the job, and select Configure.

2. In the Parameters section, click Add for each parameter:

   • Name — the Bamboo variable name (matches the mapping key).
   • Value — the default value.
   • Environment Variable — the global parameter name.

   

3. Click Submit.

Set default values in Bamboo

1. On the Bamboo dashboard, open the build plan and click Actions → Configure plan.

2. Go to the Variables tab.

3. For each parameter, fill in Variable name and Value, then click Add.

   

If the Bamboo plan uses multiple branches, add a Branch environment variable in TestOps and map it to the Bamboo variable that controls branch selection.

Troubleshooting

Bamboo finishes the build but no results arrive in TestOps

Check:

• the plan-level Allure Upload settings point to the correct TestOps endpoint and project ID;
• the job-level Test Results Directories points to the directory that actually receives Allure result files;
• the token is valid and belongs to a user who has write access to the project.

A TestOps-triggered build runs all tests instead of the selected ones

The Bamboo task that runs the tests does not expose ALLURE_TESTPLAN_PATH to the runtime. Add the environment variable mapping to the task and re-run the job from TestOps.

Related pages

• CI systems
• allurectl
• Jobs
• Environment