I have an API query that I believe was working before but now is not filtering as expected. I am trying to get pipelines but filter out any custom pipelines (just default), so I am using:
However this is now returning pipelines with target.selector.type="custom" as well.
I have also tried the following but still getting back custom pipelines as well:
Did something change, or am I doing something wrong (perhaps this was never working as expected?)
I am not sure if something has changed recently, but I believe that the following should return all builds on develop branch (and no custom builds):
Is this something that works for you?
@Theodora Boudale That answer got caught up in my junk filter, just happened to see it today. I tried that, but it didn't work. I also tried
but that completely ignores target.ref_name and returns the master branch results actually.
Hi @Jay Seletz ,
The part of the URL you posted here won't work, you don't need the 'q=' or double quotes there.
A curl command like the following returns builds that ran on branch develop for me:
curl -X GET -u username:app-password https://api.bitbucket.org/2.0/repositories/workspace-id/repo-slug/pipelines/?target.ref_name=develop
after replacing appropriate values for username, app-password, workspace-id and replo-slug.
Could you please let me know
Hi @Theodora Boudale - I did try the exact url you suggested, and while it does filter on branch correctly, the results returned also include custom pipeline runs, e.g.
I am trying to query by target branch AND selector.type=default. When I say the two approaches I've tried (without using "q=" syntax and with it), it succeeds and returns results filtered by branch, but not by type at all, when specifying
Also with the two examples I posted originally when I started this thread, the results are not filtered by type, just by branch. I believe this first url I posted (at the top of this thread) used to correctly filter by type, but no longer does, nor does any other query syntax I've tried.
Hi @Jay Seletz , thank you for your reply and explanation.
I wasn't thinking about custom builds that ran on a branch, I had in mind only custom builds that ran on a specific commit which are excluded if you specify a branch. I see what you're saying about target.selector.type not working in the filter.
I will reach out to the dev team about this issue and will get back to you as soon as I have a response.
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
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