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

Pipe to trigger a pipeline documentation seems to be inconsistent. says that the type for wait and debug are boolean.

And when I use a boolean in my pipeline, the error reports I've done exactly as requested, but that it is also wrong.

There is an error in your bitbucket-pipelines.yml at [pipelines > branches > master > 1 > step > script > 0 > variables > WAIT]. To be precise: This value should be a string (it is currently defined as a boolean).

So, for example, if I want to use OIDC, I say

oidc: true

So, I've got 

WAIT: true
DEBUG: true

 for the 2 booleans.

I'll be testing to see if these need to be strings to work. But either way, the documentation is wrong as the error reported for doing it the way the documentation says to do it is reported perfectly as the problem!

1 answer

Quoting 'true'/'false' worked, but then that's just a string.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events