Hello @MS ,
Deployment projects were designed to be separated from build dashboard. Imagine situation when you have several builds to be executed against your commit. Then deployment is different point of view on your artifact with separate lifecycle.
If your configuration allows one-to-one mapping of build plan -> artifact -> deployment. Then maybe you can make deployment phase as Manual stage of your plan:
| - Build & test stage
| |- run tests
| \- build artifacts
| - manual stage
| \- deploy artifacts
It will allow you to run deployment on demand and mark build result with outcome of deployment
thank you for the quick response. There are two build stages and two artifacts in my project. Both artifacts properties has been marked as "Shared" and "Required". I used "Triggers" functionality which allow deployment process starts right after the correct build.
In the "Other environment settings" section it is possible to set notifications for a specific person in case of deployment problem but you have to notice the email.
I do not fully understand your advice. I can add deployment as part of the project (next stage) and then I will have information about deployment on the dashboard but I would prefer to keep deployment as separate project.
Perfect solution will be checking build/ link deployment status without checking project properties but I am afraid that this is not possible at this moment. I simply wanted to know did I missed something.
We’re preparing for Bamboo 8.0, which will be our first Data Center release. To make sure our app vendors and customers with written in-house apps are prepared, we’re launching Bamboo 8.0 Early Acces...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events