Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bitbucket pipeline not picking up changed node version

Pratik Jaiswal July 6, 2021

I have changed the Node.js image in bitbucket-pipeline.yml file but still, the bitbucket pipeline is picking some other node version.

Updated node.js image

image: node:14.17.1

The old node.js image in the pipeline was

image: node:10.15.3

But bitbucket pipeline is picking up node version 10.12.0.

What am I doing wrong? Thanks in advance

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 12, 2021

Hi Pratik and welcome to the community.

I haven't been able to reproduce the issue you are reporting, when I run a build with image node:14.17.1, the command node -v gives as output v14.17.1.

An image can be defined either at a global level or at the step level, so it's possible that the step that shows an older node version is using a different image.

Can you check the bitbucket-pipeline.yml file and see if there is a different Docker image defined specifically for the step that shows an older node version?

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events