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

Curl doesn't work on only one repo

We have multiple repositories using bitbucket pipelines, however on one of them the curl command to grab nodejs isn't working like the rest. they have identical yaml files up to that point. The others with the identical curl request take like 30 seconds and output the result. does anyone have any ideas why it wouldn't be working here?

Screenshot 2021-09-30 115644.png

1 answer

0 votes

Hi Will,

Are you using the same Docker image for the step that is failing as with the steps that are successful on other repos?

You mentioned that the repos have identical yaml files; one possibility I can think of is that the yaml file may be identical on the main branch of all repos, but it may have been modified on a different branch of the repo (where builds are running) and it may use a different Docker image.

You can view the yaml file for the step that is failing if you open the failed build and select the cog icon that shows the text "View configuration" if you hover it:

Screenshot 2021-10-01 at 17.58.02.png

Keep in mind that a Docker image may be defined either globally or at the step level.

Kind regards,

Suggest an answer

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

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,461 views 3 10
Read article

Atlassian Community Events