Using stages in a plan

Stages group (or 'map') jobs to individual steps within a plan's build process. For example, you may have an overall plan build process that comprises a compilation step, followed by several test steps, followed by a deployment step. You can create separate Bamboo stages to represent each of these steps.

A stage:

  • Has a single job, by default, but can be used to group multiple jobs.
  • Processes its jobs in parallel, on multiple agents (where available).
  • Must successfully complete all its jobs before the next stage in the plan can be processed.
  • May produce artifacts that can be made available for use by a subsequent stage.

Each new plan created in Bamboo contains at least one stage (for the default job) and is known as the 'Default Stage'. Stages can only be configured by Bamboo administrators.

On this page:

About manual stages

Any stage in a plan can be configured to be a manual stage. If you run a plan with manual stages, Bamboo will pause the execution of the plan every time it reaches a manual stage. The plan build will only continue once a user has manually triggered the stage. Please note:

  • A manual stage can only be triggered if the previous stage has completed successfully.
  • Manual stages must be be executed in the order that they are configured in the plan. You cannot skip a manual stage.
  • Manual stages will be displayed in the Plan Navigator with either this icon (not due to be triggered) or this icon (pending execution).
  • You need 'Build' permission on the plan to run a manual stage.

Navigate to the stages for a plan

To navigate to the stages for a plan:

  1. Choose Build > All build plans from the Bamboo header, then click the name of the plan you want to edit.
  2. Choose Actions > Configure Plan.
  3. Click the Stages tab.

Create a stage

  1. Navigate to the stages for the plan, as described above.
  2. Click Create Stage, at the right. 
  3. Complete the form and click Create. For information about manual stages, see About manual stages above.
  4. (optional)You may want to do one or more of the following with your new stage:
    • Order your new stage in the list of stages, by dragging and dropping it.
    • Add a new job to your stage.
    • Move a job from another stage to your new stage by dragging and dropping the job.

Note that you may break artifact dependencies by moving stages, or by moving jobs between stages. Bamboo will warn you, if a dependency will be broken by moving a stage or a job.

Edit a stage

  1. Navigate to the stages for the plan, as described above.
  2. Edit the stage as required:
    • To edit the name and description of the stage or configure whether it is a manual stage, click the cog icon and choose Configure stage.
    • To move the stage, drag and drop the stage to the desired place in the plan.

Note that you may break artifact dependencies by moving stages. Bamboo will warn you if a dependency will be broken by moving a stage.

Delete a stage

Before you begin, please understand that:

  • Deleting a stage will delete all job configurations, artifacts, logs and results related to the stage. These cannot be recovered after the stage is deleted.
  • You may break artifact dependencies by deleting a stage.

To delete a stage:

  1. Navigate to the stages for the plan, as described above.
  2. Click the cog icon for the relevant stage and choose Delete stage.
  3. Click Confirm to delete the stage. Note that a deleted stage cannot be recovered.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

5 Archived comments

  1. User avatar

    Oliver Pereira

    Bamboo does not allow a single workspace to be defined for the Stages or share the workspace.

    I would like to run the integration tests and deployment in a separate stage (manually) but Bamboo creates a new workspace for each Stage and it fails because it cannot find the previous artifacts.

    This feature is completely useless for us unless there is a way to share the workspace.



    24 Nov 2014
  2. User avatar

    Sten Pittet

    Hi Oliver Pereira,

    Have you tried sharing artifacts between jobs? It's not possible to share workspaces because jobs are not necessarily run by the same agents. However by sharing specific artifacts you can run integration tests for a specific build artifact and use the same build artifact for deployments.

    Let me know if this helps,

    Sten Pittet
    Bamboo Product Manager 

    25 Nov 2014
  3. User avatar

    Oliver Pereira

    I haven't tried the sharing artifacts solution as I need to share the workspace (target folder) and they are quite large considering our company produces games and I will have to spend time clearing disk space, which is another additional operation overhead.

    There are quite a few basic features that are missing in Bamboo but are available in other open source or paid products for a number of years now. Unfortunately it's not just about writing code, committing it and the leaving the CI to do the rest. I spend a lot of time debugging broken builds on the CI environments and there are quite a few useful features missing in Bamboo, which can help users like me a lot.

    I had to do a analysis of the various CI tools available in the market to replace our Hudson instance and I had nailed it down to TeamCity as it provides ALL the features we were looking for while Bamboo doesn't. But the company had already purchased the license for Bamboo and we decided to go with Bamboo.

    Currently there are critical bugs in Bamboo and I raised them in your JIRA bug tracker but they seem to have been completely ignored.

    I am more than willing to take this offline and discuss it but I don't have my hopes high as the history shows a lot of requests have been conveniently ignored over the years.

    25 Nov 2014
    1. User avatar

      Sten Pittet

      Please send me an email at so that we can arrange a discussion. I'd really like to get your feedback on the missing features that could help you with your CI process.

      We are always welcoming feedback from our customers whether it is on or via other means (interviews,, support...). We try to address those requests to our best ability but we sometimes have to do tradeoffs due to the priorities on the roadmap and the complexity of the challenges. We also intentionally limit the number of features in each release to have a stronger focus on quality.

      I'm sorry to hear that you're having trouble with Bamboo and I wanted to provide more context to understand how we plan our releases. Please don't hesitate to send me an email so that we can discuss together.



      25 Nov 2014
  4. User avatar

    sendami linan

    Excuse me, was this question resolved?

    24 Apr 2015
Powered by Confluence and Scroll Viewport