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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,455,415
Community Members
 
Community Events
175
Community Groups

How do you use different Node.js versions on build machine?

We need the ablility to reproduce older builds.  So in the future we will need to build with the older version of Node.js along with the future versions for future builds.  This is all on one build machine. 

1 answer

0 votes
devpartisan Atlassian Team Aug 30, 2017

I run into this all the time, not just on the Bamboo server, but on my local dev machine. I have found Node Version Manager (nvm) to be a huge help for both cases. To install a given version (and keep it around), just do "nvm install 0.10". In a Bamboo build, you would just run a script task for "nvm use 0.10" then you can kick off your build however you would normally.

This is great post and quite simple.  By setting a default version nvm alias default <version>, any other shell that opens will use this.  Then in my build job, I just add a script shell and call nvm use <myVersion> and run the build.  When finished, no harm done.  Everything (other builds) just looks the same.  

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events