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

When condition is not met for a conditional task, why the whole build fails?

I have a conditional task for which i have used a plan variable isRCBuild to trigger.

When isRCBuild=0 it should run otherwise no.

When the isRCBuild=1 the condition is not met but the whole builds stops, why is that? shouldn't it just be skipped??


1 answer

1 accepted

0 votes
Answer accepted
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 03, 2020

If it's the only task then build fails because there were no tasks for execution. Add dummy Script task "echo hi" to avoid it

If it's only task then it should go to next job. I think this qualifies as a bug.

@Alexey Chystoprudov Do you think this should qualify as a bug?

For the workaround, i now check the bamboo variable from the script itself and EXIT if required. Bamboo conditional tasks are not that robust from my POV.

Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 05, 2020

@Chitrarth Sahai , it's existing behaviour. When you create job without task Bamboo fails it as we decided it's not a good situation.

The same when all tasks are skipped, it means job had no executable tasks and its state is unknown. 

Well then it would be nice if there was a conditional Job and not just conditional tasks :)

Right now the only way to get a conditional job, is to set the same condition on each task in the job, except a final dummy task that always runs.  That seems like a bad way to have something change in the future, but forget to change it everywhere.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events