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,556,190
Community Members
 
Community Events
184
Community Groups

Is it possible to block environment from manual start in deployment plan

Hi, here is little diagram:

Untitled Diagram.png
Env1 and Env2 are deployed in parallel by deployment plan; Final env shall be triggered manually whenever suited. I want to safeguard myself from situation, when someone triggers final environment manually before  Env1 or Env2 have finished execution.
Is it possible by standard means of Bamboo or I shall go into scripting?

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 02, 2019

Hi @Anton_Kuryan

we don't have any mechanism in Bamboo to can prevent that.
I was trying to find a way to solve this problem and the best I could think of was somehow failing the final deployment when the results of Env1 and Env2 are still not available.

We don't have such restrictions or dependence between environments.

  • Do you want me to create a feature request for that?
  • If the answer is yes, what would be the format of this feature? Can you give me more details on how you see that this feature could work?

Yes, I would like to see it as a feature request, possibly coupled with another possibility: "and" behavior for Environment deployment switch (so, Final env shall be possible to start via Successful deployment trigger, which starts it only in case both envs are OK).

Format of a feature - maybe a dropbox at environment configuration which will say that environment is dependent on some other environments (so, I could select several with checkboxes, much like rights are assigned).

Can you advise on API call which I can use to track the status of previous environments?

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 15, 2019

Hi @Anton_Kuryan

I'm sorry for the delay here, I needed some quiet time to work on this and it was difficult to find.

This is the feature request I created based on your comment:

This is a feature request that is related to the one we just created and could be of your interest:

Can you advise on API call which I can use to track the status of previous environments?

I created this community article to allow you getting the environment result information you need from REST API:


Please add yourself as a watcher and vote in the feature requests above. If you have more comments on this matter, just let me know.

Like Anton_Kuryan likes this

Thank you. I will look into it

Like Daniel Santos likes this
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 15, 2019

You are welcome! =]

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events