![]() |
|
|
|
|
Change By:
|
Travis Cosgrave
(22/Aug/14 2:16 PM)
|
|
Summary:
|
NodeJS Plugin
installs
runs auto-install
while other
dependant
jobs are running, breaking builds
|
|
Description:
|
I have
With
multiple jobs configured to use the same NodeJS Installer
. As a result
,
sometimes one
say
job
is running
A and job B,
the
installer to update the cache while another one starts. It seems as if all of node is removed making commands unavailable. It looks like it's event happened during a build resulting
auto-install option results
in
job B failing when job A triggers
a
file not found error
NodeJS install
.
Is there a way
This is especially an issue when multiple jobs relying on the same NodeJS install are triggered
to
share
run at the same time via source control, and all of the jobs try to use
a
node js installer with multiple builds
package
that
may run concurrently?
has been removed by first the auto-install process.
This is the error I received during the middle of my job, after
already
using
this package a whole bunch of time before
the
error
referenced module during the running job
.
{code}
Error: ENOENT, no such file or directory '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/'
at Object.fs.readdirSync (fs.js:654:18)
at loadCommandFiles (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:166:27)
at loadClientCommands (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:158:5)
at module.exports.load (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:381:5)
at new Nightwatch (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:41:18)
at Object.exports.client (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:432:10)
at runModule (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:142:27)
at runTestModule (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:481:7)
at null._onTimeout (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:484:13)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
ENOENT, no such file or directory '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/'+ true
{code}
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
