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

Query Bitbucket API for occurrences of a custom pipeline


I'd like to query the Bitbucket API for occurrences of a specific custom pipeline. I've tried various incarnations of the filtering syntax, but it never seems to filter anything.

Here's the basic curl invocation I've got.

curl -G --fail \
--data-urlencode 'q=target.selector.pattern = "$RULE"' \
--data-urlencode 'sort=-created_on' \
--data-urlencode '*,values.created_on' \
--data-urlencode 'page=1' \
--data-urlencode 'pagelen=10' \

Is this possible? I've seen other answers show that querying by branch (for example) doesn't even use the filtering syntax (e.g., just "target.branch=master"), so I'm at a loss for how to move forward.

2 answers

I'm also running into this now, it seems like `q` just isn't implemented on this endpoint. Not sure if this is a bug or just a missing feature, but I would love to upvote it to see it made usable.

Otherwise, there's no real workaround other than polling for every single pipeline in the entire history of the repo, which is obviously untenable.

Very sad right now. I can't query to find the last successful deployment with a specific tag prefix. So that means I cannot re-deploy the last successful deployment. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events