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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Bamboo Deployment plan - determining cause of trigger

In our bamboo deployment environments, we would like to execute a task step only if it was manually triggered by a user. If it was triggered using an automatic trigger like scheduled or after another successful deployment, we would like to skip a task. Is there a way to achieve this?

1 answer

0 votes
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 05, 2019

This could work.

But we want a certain thing to happen when deployment environment is automatically triggered vs we do not want it to happen when the environment is manually triggered. We will need a mechanism to add multiple users in the condition or need to know what the username will be when the job is automatically triggered. It seems we can have only one username used in the condition. 

Another way would be to have a variable that would set (or unset) for manual deployment vs automatically triggered deployment.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events