There's a free plugin that provides this functionality: https://marketplace.atlassian.com/apps/1216136/after-deployment-trigger-for-bamboo

I just want to know what's the status for this tix right now, solved? 

@Alex thanks for the update.

e8f062a9d47a it's not possible right now. We're working at this feature https://jira.atlassian.com/browse/BAM-12095 and hope it will be part of 6.10 we're going to release in few weeks

As per the official docs bamboo supports only

• user (user name)
• password

https://bobswift.atlassian.net/wiki/spaces/ACLI/pages/392757809/Authentication

@Ernest @Lars @Kelly,

Is there any way to authenticate bamboo rest call using a token instead of user id and password?

In my current project, the bamboo is owned/controlled by an external central team, they don't want to provide the user id and password to individual teams.

Seems like they changed the Rest method for this. Now you have to use PUT instead of POST.

Wow, thank you Earnest I that is the best explanation I've seen on the Internet of how to do this.  My biggest error was having Build and Tests in different build plans.  Thus making it impossible to trigger different deployment environments.  Once that was setup then I thought I would detail that next step a little more.

To trigger a build plan from a deployment plan, the last task needs to do a 

curl -X POST -u admin:admin  https://mycompany.com/bamboo/queue/$\{bamboo_buildResultKey}?stage=Stage%20Name&executeAllStages=false

 Documented at

That call resumes the build from where it left off at the stage "Stage Name"and it executes only that stage.

Fantastic again my thanks

You just do the same thing and chain it.  We have a build that has a build stage (auto), a test CI stage (manual), and a test prod stage (manual). Then we have a deployment project with two environments defined, CI and Production.  The CI deployment triggers on successful completion of the build stage, the prod deployment triggers on successful completion of the test CI stage.  Then both the CI and prod deployments have a final task that hits /rest/api/latest/queue/${bamboo_buildResultKey} with the name of the next build stage.  

So the build plan runs, and the initial build stage runs.  It stops. The CI deployment triggers off it, runs, and kicks off the CI test part of the build job. It stops.  The prod deployment triggers off that, runs, and kicks off the prod test part of the build job.  Works, and also you have the benefit of the build job going red if deployments fail (devs can somewhat be convinced to watch if their build light is red or green, but can never be convinced to also go check if the deployment plan lights are red or green).

I should probably clarify, each test(build plan) is setup to run against different environments.  How can I do this right now?