You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAHDZtpROhk9LpbZrzAPyKpeKmmZ9-rhwe7ptQFMdZv3ti69REw%40mail.gmail.com.
pru7@pru7s-Mac-mini one-pulse-app % npm --version
pru7@pru7s-Mac-mini one-pulse-app % java --version
openjdk 11.0.7 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
pru7@pru7s-Mac-mini one-pulse-app % which npm
pru7@pru7s-Mac-mini one-pulse-app % cd
pru7@pru7s-Mac-mini ~ % command -v npm
pru7@pru7s-Mac-mini ~ % ls -l $(command -v npm)
lrwxr-xr-x 1 root wheel 38 Jun 19 2020 /usr/local/bin/npm -> ../lib/node_modules/npm/bin/npm-cli.js
pru7@pru7s-Mac-mini ~ %
Were you execing npm as the same agent user?Probably be good to find the path the npm and show its permissions bitstry:1) command -v npm2) then: ls -l $(command -v npm)That should tell us the location of the binary and the flags. Just need to do a sanity check since I’m not certain where else to start until we verify these. The screenshot reported the value of the PATH variable, so just making sure npm is under that. When you execute manually, your PATH may be different from when invoked by gocd.
Hmm, that’s right npm really just wraps node. So you’ll have to change your PATH to include /usr/local/binYou can do this in the wrapper properties for the agents.You should be able to add:set.PATH=/usr/local/bin:/usr/bin:...
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAPKX9jb5oB-i6qUSTkrzMWcSuHMC675aa2pCpaHSTHdm3rFj3g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CANiY96ZQ2AkS6-g_XbBZ3sECL5siDENpBkZ_wZrwTGV-v2UdPQ%40mail.gmail.com.