Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Managing multiple node versions

I'm trying to figure out how to manage multiple node versions for a variety of different projects for our Bamboo server.

 

I can't seem to figure out how to include multiple versions of node from 0.10 to 5.0.0 in bamboo and have projects build from differing versions of node while managing the node_modules folder.

 

What is the best way to handle installing/handling multiple node versions and builds?

 

Thank you

2 answers

0 votes
nriley Atlassian Team Dec 02, 2015

NVM is a useful tool, depending on the complexity of the environment you are trying to test with:

https://github.com/creationix/nvm

This would allow you to declare a specific version of node via the command-line, and subsequently execute the corresponding code with whatever node_modules folder you needed.

I would suggest caching the request to the NVM script (from the link above) so you could control how this was being executed in your own environment (rather than relying on a 3rd party source).

nriley Atlassian Team Dec 02, 2015

To further develop this answer: If you were looking to do something which ran multiple versions of node on the same agent, you could bypass the node path and directly access the place that nvm stores the node binary and global node_modules. For each version of node, the path is switched accordingly. A question: Are you trying to run multiple versions of node in tandem with each other on the same agent? If so...why? Would a docker-ized solution work better for this kind of situation?

We'll try out the NVM solution just to try it out. We're trying to stay away from having to set up dockers. We have use cases across multiple versions of node and RHELS

how do you switch the node versions using the Bamboo Node.js Plugin?

@Joseph Kim  how did you resolved the issue?? I used NVM. Just installed in my server and and when running bamboo task. It doesn't recognize nvm  or node as commands.

But when only node.js is installed , bamboo recognizes node command. 

Can you help me with that please... 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
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