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

Bitbucket API bug: links returned from pipeline trigger will 404

I think this is a bug with the Bitbucket API.

I triggered a pipeline build with a curl like:

curl \
-s \
--fail-with-body \
--user blah:blah \
-H 'Content-Type: application/json' \ \
-d '{...}'

...and it triggered fine. The response includes this fragment:

"links": {
"self": {
"href": "}/repositories/zzzzf159-d03c-4508-a9cb-fa5a922e7e07}/pipelines/zzzz4283-b506-43eb-a8b5-376806f99be6}"
"steps": {
"href": "}/repositories/zzzzf159-d03c-4508-a9cb-fa5a922e7e07}/pipelines/zzzz4283-b506-43eb-a8b5-376806f99be6}/steps"

...but when I tried to GET either of those URLs, I get a 404. When I remove the double slash at the end of the hostname (``), then I get a better response. I actually get a 401, but that probably is something I'm doing wrong.

The point is that the server probably has a trailing slash configured on the prefix that is prepended to the rest of the URL that's returned to the caller.

1 answer

1 vote

Hi Tom,

This is indeed a bug, the urls that are returned are internal urls and cannot be used to retrieve the pipeline or the steps.

We have a bug report about this in our issue tracker:

The way to work around this at the moment would be to manually assemble the url instead of using the ones in the response{workspace}/{repo_slug}/pipelines/{pipeline_uuid}{workspace}/{repo_slug}/pipelines/{pipeline_uuid}/steps/

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events