Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,703
Community Members
 
Community Events
176
Community Groups

Deployment plan result show in plan status

Is it possible to change the status of the plan to unsuccessful if the deployment plan was unsuccessful? Although, the plan itself has been ok (stages and tasks)?

1 answer

0 votes

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:

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

Hello Alexey,

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events