You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.