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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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.

@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. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center is here!

G’day Bamboo customers, The wait is over! Bamboo Data Center edition you have been asking for is finally here! This self-managed enterprise offering of Bamboo has the resilience, reliability, and s...

501 views 1 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you