Re: [Apiman-user] building apiman on Redhat

Wednesday, 15 June 2016

Hi Rachel,

Thanks for your response.  There are a few things here which are confusing me:

1. the build log says "Running 'npm install --color=false' in
/var/lib/jenkins/jobs/Upgrade APIMAN/workspace/manager/ui/war"

is that correct? (it seems like it's trying to run a globally installed npm...) If
it's trying to use a locally installed npm, why isn't is using a relative path to
it?

2. If I change manager/ui/war/node/npm so that NODE_EXE=./node/node (instead of
"node")  it succeeds.

3. The failing job is being run by Jenkins, and the Jenkins user has no node on it's
path. But if I run the build as a different user who does, it works.

It seems that the plugin which installs nodejs locally, or some subsequent part of the
build process, isn't referring to them correctly (and thus is dependent on a globally
installed node in order to work).  Any insight? For what it's worth I can build the
exact same source, from the same repo, with the same command, on my mac, which has node
and npm installed globally.

Thanks,

Chris

________________________________
From: Rachel Yordan <ryordan(a)redhat.com&gt;
Sent: Wednesday, June 15, 2016 1:21:53 PM
To: Christopher Stolte
Cc: apiman-user(a)lists.jboss.org
Subject: Re: [Apiman-user] building apiman on Redhat

Hey Chris,

When you run `$ npm install` or even `$ node -v` you are using the globally installed
binary as opposed to the local one, even if you are within the directory, as you can see
here:

npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm"
"install" "--color=false"

The deprecation warning at the end of the build log should not be enough to cause a build
failure. To get a more detailed error regarding the build failure I'd try using the
local binary from within the `war` directory you were in with `$ node/npm install
--color=false`. You can also test that it's using the correct binary with `$ node/npm
-v` or `$ node/node -v`. What is causing the build to fail could be several things, but I
always recommend starting with a clean slate before each test build -- try running the
following before triggering your build again:

$ rm -rf node_modules/
$ npm cache clean

Feel free to ping me on IRC if that doesn't help you get a better idea of what's
going on. Hope it helps! :)

Rachel Yordán
IRC: ryordan
GH: @kahboom<https://github.com/kahboom>

On Wed, Jun 15, 2016 at 10:59 AM, Christopher Stolte
<cstolte@ebsco.com<mailto:cstolte@ebsco.com>> wrote:

Hello,

I am trying to build apiman-1.2.6.Final on Redhat.  Server details:

$ uname -or

3.10.0-229.el7.x86_64 GNU/Linux

$ java -version

openjdk version "1.8.0_91"

The build fails at this point:

[INFO] --- frontend-maven-plugin:0.0.27:install-node-and-npm (install node and npm) @
apiman-manager-ui-war ---

[INFO] Found proxies: []

[INFO] Installing node version v5.6.0

[INFO] Creating temporary directory /home/cloud-user/apiman-build/manager/ui/war/node_tmp

[INFO] Downloading Node.js from
https://nodejs.org/dist/v5.6.0/node-v5.6.0-linux-x64.tar.gz to
/home/cloud-user/apiman-build/manager/ui/war/node_tmp/node.tar.gz

[INFO] No proxies configured

[INFO] No proxy was configured, downloading directly

[INFO] Extracting Node.js files in node_tmp

[INFO] Unpacking /home/cloud-user/apiman-build/manager/ui/war/node_tmp/node.tar.gz into
/home/cloud-user/apiman-build/manager/ui/war/node_tmp

[INFO] Moving node binary to /home/cloud-user/apiman-build/manager/ui/war/node/node

[INFO] Deleting temporary directory /home/cloud-user/apiman-build/manager/ui/war/node_tmp

[INFO] Installed node locally.

[INFO] Installing npm version 3.6.0

[INFO] Downloading NPM from http://registry.npmjs.org/npm/-/npm-3.6.0.tgz to
/home/cloud-user/apiman-build/manager/ui/war/npm.tar.gz

[INFO] No proxies configured

[INFO] No proxy was configured, downloading directly

[INFO] Extracting NPM files in node/

[INFO] Unpacking /home/cloud-user/apiman-build/manager/ui/war/npm.tar.gz into
/home/cloud-user/apiman-build/manager/ui/war/node/node_modules

[INFO] Installed NPM locally.

[INFO]

[INFO] --- frontend-maven-plugin:0.0.27:npm (npm install) @ apiman-manager-ui-war ---

[INFO] Found proxies: []

[INFO] Running 'npm install --color=false' in
/home/cloud-user/apiman-build/manager/ui/war

[ERROR] npm WARN deprecated graceful-fs(a)1.2.3: graceful-fs v3.0.0 and before will fail on
node releases >= v7.0. Please update to graceful-fs(a)^4.0.0 as soon as possible. Use
'npm ls graceful-fs' to find it in the tree.

Node/npm appear to be globally installed:

$ npm -v

2.15.1

$ node -v

v4.4.3

I then tried to execute that npm command from the stated directory, and got this:

$ cd manager/ui/war

$ npm install --color=false

npm WARN peerDependencies The peer dependency marked(a)^0.3.3 included from marked-terminal
will no

npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency