Once you have created and configured your new deployment project, you can create environments for it to deploy to. Bamboo allows you to create multiple deployment environments and also allows you to manage:

  • Environment details such as name and description
  • Tasks
  • Triggers
  • Permissions
  • Agents
  • Notifications
  • Variables

To create a new deployment environment you will need to:

  1. Provide a name that represents your environment e.g. Test or Production
  2. Provide a description that describes the function of your environment.

On this page:

Related pages:

Deployment environments are added from the Deployment project configuration screen:

Creating a new deployment environment

To create a new deployment environment:

  1. Click the blue Add environment button from the 'Deployment project configuration' screen. The 'Set up environment' screen will display:


  2. Complete the 'Set up deployment project' screen using the following fields:

    Field
    Description
    Optional?
    Environment nameThe name of the environment(error)
    DescriptionA brief description of your deployment project(tick)
  3. Click on Create and back to create the environment and return to the 'Deployment project configuration' screen. 
    Note: Because no tasks have been defined for this environment, it will appear with a red exclamation mark:


    Alternatively, click on Continue to task setup to continue to task setup for your new environment:


    See Tasks for deployment environments for more information on task configuration.

Using the deployment environment panel

All deployment environments are managed from the Deployment project configuration screen. By default, when the screen loads, each environment panel is displayed in its collapsed state. Click Edit to expand the deployment environment panel:

When expanded, the environment panel shows three separate sub-panels:

The three sub-panels provide the following functionality:

Sub-panelFunctionalityDescription
Environment
  • Deploy
  • Actions
  • Minimise
  • Manually deploys to the environment
  • Allows the user to View, Delete or Move down the environment
  • Minimise the environment panel back to its collapsed state
How you want to deploy
  • Edit tasks
  • Allows the user to edit the tasks associated with the environment
Other settings
  • Triggers
  • Environment permissions
  • Agents
  • Notifications
  • Variables
A set of optional settings that make your Bamboo deployments run more smoothly

Editing the environment details

Bamboo allows you to change both the environment name and the description. To edit these details:

  1. Expand the environment panel and click the pencil icon next to the environment name. The 'Update environment' screen will display:


  2. Complete the 'Update deployment project' screen using the following fields:

    Field
    Description
    Optional?
    Environment nameThe name of the environment(error)
    DescriptionA brief description of your deployment project(tick)
  3. Click Save environment to save your changes.

 

  • No labels

1 Comment

  1. Richard Barbalace

    Oct 30, 2013

    There seems to be a vital piece of information missing here:  How do you tie environments to branches?

    I have set up a build project with branches:  Development, QA, Staging, and Master.  These are linked to the branches on my GIT repository and they build successfully using those branches.

    I have also set up environments:  Development, QA, Staging, Production, and Demo.  When I create a release, it is linked to the build project (specifically the default Development branch of source repository).  There does not appear to be a way to link a release to a different branch.

    I want to specify the branch to use for the release so I can link the appropriate source repository branch to the appropriate environment.  That is, I want to create a Development release from the Development branch that I can deploy to the Development environment, a QA release from the QA branch that I deploy to the QA environment, a Staging release from the Staging branch that I can deploy to the Staging environment, and a Master release from the Master branch that I can deploy to the Production and Demo environments.

    How do I do this?  Or is there some other prefered way of accomplishing this?