search

Strider-CD / strider-node

Run Node.js tests in strider
11 stars 13 forks source link

multiple versions of node #3

Open jaredly opened 11 years ago

jaredly commented 11 years ago

What's the best way to handle this? Currently, n is used which downloads the version you want every build. This is annoying and adds >10 seconds to your build.

Suggestion: strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and 0.11. Then on each build you wouldn't need to download them, just copy them to the appropriate directories.

niallo commented 11 years ago

So this is what engineer is for: https://github.com/niallo/node-engineer

Might need some updates but basically cache whatever is required install from binary with nave if not.

Sent from my iPhone

On Sep 28, 2013, at 9:40 PM, Jared Forsyth notifications@github.com wrote:

What's the best way to handle this? Currently, n is used which downloads the version you want every build. This is annoying and adds >10 seconds to your build.

Suggestion: strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and 0.11. Then on each build you wouldn't need to download them, just copy them to the appropriate directories.

— Reply to this email directly or view it on GitHub.

jaredly commented 11 years ago

Awesome.

On Sun, Sep 29, 2013 at 1:47 PM, niallo notifications@github.com wrote:

So this is what engineer is for: https://github.com/niallo/node-engineer

Might need some updates but basically cache whatever is required install from binary with nave if not.

Sent from my iPhone

On Sep 28, 2013, at 9:40 PM, Jared Forsyth notifications@github.com wrote:

What's the best way to handle this? Currently, n is used which downloads the version you want every build. This is annoying and adds >10 seconds to your build.

Suggestion: strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and 0.11. Then on each build you wouldn't need to download them, just copy them to the appropriate directories.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider-node/issues/3#issuecomment-25327617 .

knownasilya commented 10 years ago

@jaredly @niallo how would we integrate node-engineer?

jaredly commented 10 years ago

have it installed, and then instead of running npm install, we run engineer -f package.json -c "npm install"

niallo commented 10 years ago

yep, exactly.

On Monday, October 6, 2014, Jared Forsyth notifications@github.com wrote:

have it installed, and then instead of running npm install, we run engineer -f package.json -c "npm install"

— Reply to this email directly or view it on GitHub https://github.com/Strider-CD/strider-node/issues/3#issuecomment-58034330 .

Niall O'Higgins W: http://niallohiggins.com E: n@niallo.me T: @niallohiggins

knownasilya commented 9 years ago

What about the user select for a node version, would that still be done with n?