Curl doesn't work on only one repo

[Will Plaisance]

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?

[Theodora Boudale]

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:

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

Kind regards,
Theodora