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.

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

7 Comments

  1. Anonymous

    There appears to be no way to create a deployment environment for a specific branch. I support for branches planned?

    1. Anonymous

      Is it correct that deployed artifact can be from any branch?

    2. James Dumay

      We couldn't fit branch deployments in to the final release in time but its the next big thing we are going to do. You can track its progress on  BAM-13268 - Getting issue details... STATUS . Please watch and vote for this (smile)

  2. Rodolfo Romero (Cisco)

    Bamboo 5.2 allows to deploy from branches. Can this page be updated with the respective information?

  3. NathanA

    Hi Rodolfo,

    All of the documentation relating to deploying from branches is found here:

    Deployments from branches

    and here:

    Creating and configuring a deployment project

    Please let us know if these pages don't answer your questions.

     

  4. Glenn Attridge

    I'm looking for a way to define custom requirements to narrow down the list of matching build agents capable of running my deployment project, but I'm not finding where to configure this.  Am I missing something or is this currently unavailable? (running Bamboo version 5.0.1)

  5. Tim Petermann

    Is there a recommended workflow for projects which use several long-running release branches? For example, after deploying v2.4 to production we might have to ship a patch for v2.3. Is it advisable (or even possible) to do this in a single production environment?