After installing the Bamboo plugin, you can launch sandboxes from your Bamboo plan. Note that this plugin only supports sandbox environments.

Use the available build steps to create a sandbox with necessary tasks from any blueprint, retrieve its details, start your tests and end the sandbox when it's no longer needed.

Launching a Sandbox from your Plan

Open Bamboo and perform the following steps:

1. From the top toolbar, click Projects.
2. From the list, click the Project you want to work with.
3. From the list, click the Plan you want to work with.
4. From the Actions drop-down menu, select Configure plan.
5. On the Stages tab, select the job to execute.
6. Click Add task.
7. The Task types menu displays. Search for Colony. Click the Start Colony Sandbox button and update the following parameters. When done, click Save.
   • Space Name: Enter the name of your CloudShell Colony space.
   • Blueprint Name: Enter the name of the environment blueprint you would like to use for creating this sandbox.

     NOTE: To specify one of the CloudShell Colony's sample blueprints, use a [Sample] prefix, i.e. [Sample]Java Spring Website AWS EU (Ireland) or [Sample]Java Spring Website Azure (West US).

   • Sandbox name: Enter a name for your sandbox.

     NOTE: Make sure this is descriptive so you will easily find the Sandbox in the future.

   • Sandbox Id Output variable: Enter the name of the variable that will store the ID of the sandbox (default is Sandbox_Id). In the next tasks it will be available with ${bamboo.Var_Name}.
   • Artifacts: If your blueprint requires artifacts, enter a comma separated list of artifacts in the following format: [artifact name]=[artifact location].
   • Inputs: If your blueprint requires inputs, enter a comma separated list of inputs in the following format: [input name]=[input value].
8. Repeat step 7 for the Wait for Colony Sandbox and End Colony Sandbox tasks.
9. From the Run drop-down menu, select Run plan.

NOTE: In AWS environments, the applications may be inaccessible immediately after the environment becomes Active. This issue should resolve itself within a few moments when the AWS DNS propagation process completes.