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 pipeline not picking up changed node version

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

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,

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...

2,247 views 2 9
Read article

Community Events

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

Events near you