How to trigger a project deployment from a Success Build if the build has 2 Stages and the 2nd stage is manual

[Dana Cleveland]

So I have some developers that have 2 stages on their builds

Stage 1: Essentially performs a standard maven build, and always runs

Stage 2: Is a Manually triggered Stage that does a maven release:prepare / release:perform

They then have an Environment on their associated Deployment Project set to trigger on a sucessful build. 

The Environment then pushes a different artifact to our application servers which does not reside in our shared maven repos.

The trouble is that the the trigger does not happen even though the build is successful, Its a Green Circle, with a dot on the middle, vs.. a green circle with a checkmark.. So its more like "Successful Build But....." status..

How do others do it..

Because our Bamboo crosses spans the company and different teams we have agents that essentially have different credentials/permissions, we use a Requirement on the Build to help choose the Agent to run and thus the permissions to push the release to our shared maven repos, and permission to git repo for the commands that maven runs with git outside of bamboo..

[pradhyumna shrestha]

Haven't had that situation but you might want to try , I hope i helps

Bamboo Command Line Interface

use queuebuild from bamboo commandline interface.

https://bobswift.atlassian.net/wiki/display/BCLI/Documentation#Documentation-queueBuild

https://bobswift.atlassian.net/wiki/display/BCLI/Bamboo+Command+Line+Interface;jsessionid=722138E006F75794083626B8240706C4

[Dana Cleveland]

A Related Deployment Project does not seem treated as "Dependency" for the build, so it doesn't seem to let it run 

[pradhyumna shrestha]

Try this option.image2014-10-24 9:56:58.png