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..
Haven't had that situation but you might want to try , I hope i helps
use queuebuild from bamboo commandline interface.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot