Thanks for the tips and workarounds! I learned that nodejs -v works. Seems that Debain has decided to use usr/bin/nodejs instead of usr/bin/node (used on mac and windows). Terrible decision. https://groups.google.com/forum/#!topic/nodejs/Z8F8uDXY8XE
On Wed, Nov 19, 2014 at 2:52 PM, jun aoki <[email protected]> wrote: > Steve, > Just FYI Ambari team works around it in 2 ways. Installing node on the fly > and also doing the same in Docker containers. > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-Commit/ > <-- on the fly > > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-Commit-docker/ > <--- docker > > On Wed, Nov 19, 2014 at 10:09 AM, Steven Gill <[email protected]> > wrote: > > > Doing a shell command for jenkins, node -v will return > > + node -v > > /tmp/hudson1841044786601466903.sh: line 15: node: command not found > > > > Strangely enough, npm is in my path and works. > > > > Do I need to install nodejs into my workspace manually and add it to my > > environment variables? > > > > This seems like a bug to me. > > > > Issue at https://issues.apache.org/jira/browse/INFRA-8647 > > > > -Steve > > > > > > -- > -jun >
