-
Notifications
You must be signed in to change notification settings - Fork 27.4k
chore(jenkins): run Jenkins builds on Node 4 (via nvm) #13568
Conversation
bf266b6
to
ae14419
Compare
#!/bin/bash | ||
|
||
# Install nvm for this shell | ||
source ~/.nvm/nvm.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does jenkins provide this (i.e. where does it come from)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is manually installed on the server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we print the nvm/Node/npm versions used? Could be useful for debugging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it does do that automatically...
+ scripts/jenkins/set-node-version.sh
v4.2.3 is already installed.
Now using node v4.2.3 (npm v2.14.7)
source ~/.nvm/nvm.sh | ||
|
||
# Use node.js at 4.2.x | ||
nvm install 4.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is nvm install ...
sufficient or do we also need nvm use ...
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvm install
is sufficient.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4
would be enough, the latest 4.x.y
release is an LTS, it so happens it's 4.2.y
in fact.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the node.js docs:
Minors: Minors are the addition and refinements of APIs or subsystems. They do not generally change APIs or introduce backwards compatible breaking changes, except where unavoidable. These are mostly completely additive releases.
I think it is safer to stick with a fixed minor release for automatic updates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. It doesn't matter here anyway as there will be no Node.js 4.3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.