[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules

0 views
Skip to first unread message

david.weber.schenker@gmail.com (JIRA)

unread,
Feb 9, 2017, 4:55:01 AM2/9/17
to jenkinsc...@googlegroups.com
David Weber created an issue
 
Jenkins / Bug JENKINS-41876
Not respecting configuration in regards of global modules
Issue Type: Bug Bug
Assignee: Unassigned
Components: nodejs-plugin
Created: 2017/Feb/09 9:54 AM
Environment: Jenkins 2.44 on CentOS6, CentOS slave
Priority: Blocker Blocker
Reporter: David Weber

I have installed version 1.0.1 of this plugin
The installation of node and also of configured modules works good. But if I add an additional build-step with executing shell, the npm command is not found.
With version 0.2.2 this is working.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

david.weber.schenker@gmail.com (JIRA)

unread,
Feb 9, 2017, 4:59:01 AM2/9/17
to jenkinsc...@googlegroups.com
David Weber updated an issue
Change By: David Weber
I have installed version Version: 1.0.1 of this plugin
The
h4. Current state
If I have a nodejs installation of node and also of configured to not install any global modules works good , it will not be respected . But if I add an additional  build-step
The command will anyway execute with executing shell, the " npm command install -g" which is not found valid .
 With version 0
{noformat}
$ /Users/<user>/ . 2 jenkins/tools/jenkins . 2 this plugins.nodejs.tools.NodeJSInstallation/NodeJS_6.9.4/bin/npm install -g
npm ERR! Usage:
npm ERR!     npm cache add <tarball-url>
npm ERR!     npm cache add <pkg>@<ver>
npm ERR!     npm cache add <tarball>
npm ERR!     npm cache add <folder>
npm ERR!
{noformat}

h4. Expected behavior
The command "npm install -g " will not run if there is working no configuration for global modules .

david.weber.schenker@gmail.com (JIRA)

unread,
Feb 9, 2017, 4:59:01 AM2/9/17
to jenkinsc...@googlegroups.com
David Weber updated an issue
Change By: David Weber
Environment: Jenkins 2.44 on CentOS6, CentOS slave macOS

nfalco79@hotmail.com (JIRA)

unread,
Feb 9, 2017, 8:47:02 AM2/9/17
to jenkinsc...@googlegroups.com
Nikolas Falco commented on Bug JENKINS-41876
 
Re: Not respecting configuration in regards of global modules

Can you post here the global configuration settings of your NodeJS_6.9.4.
Can you also attach your jenkins.plugins.nodejs.tools.NodeJSInstallation.xml in jenkins home folder?

The only reason that could happens npm install -g if that the list of global configuration are not empty (maybe spaces). With the configuration and specially with file I can see what is persisted.

nfalco79@hotmail.com (JIRA)

unread,
Feb 9, 2017, 10:49:01 AM2/9/17
to jenkinsc...@googlegroups.com

As possible workaround:

  1. edit jenkins global configuration tool
  2. remove all possible white spaces from list of "global npm packages"
  3. save and launch a build again

regs@akom.net (JIRA)

unread,
Feb 10, 2017, 6:23:02 PM2/10/17
to jenkinsc...@googlegroups.com
Alexander Komarov updated an issue
 
Change By: Alexander Komarov
Attachment: Screenshot_2017-02-10_16-21-49.png

regs@akom.net (JIRA)

unread,
Feb 10, 2017, 6:23:02 PM2/10/17
to jenkinsc...@googlegroups.com
Alexander Komarov commented on Bug JENKINS-41876
 
Re: Not respecting configuration in regards of global modules

I'm seeing the same thing, confirmed no spaces in global npm packages field, saved again.

00:00:08.923 $ /data/jenkins-slave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin/npm install -g 
00:00:09.597 npm ERR! Usage:
00:00:09.598 npm ERR!     npm cache add <tarball-url>
00:00:09.598 npm ERR!     npm cache add <pkg>@<ver>
00:00:09.598 npm ERR!     npm cache add <tarball>
00:00:09.599 npm ERR!     npm cache add <folder>
00:00:09.599 npm ERR! 
00:00:09.611 ERROR: Build step failed with exception
00:00:09.611 java.lang.NullPointerException
00:00:09.612 	at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:92)
00:00:09.612 	at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:87)
00:00:09.612 	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
00:00:09.612 	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
00:00:09.612 	at hudson.remoting.Request$2.run(Request.java:324)
00:00:09.613 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
00:00:09.613 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
00:00:09.613 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
00:00:09.613 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
00:00:09.613 	at hudson.remoting.Engine$1$1.run(Engine.java:63)
00:00:09.614 	at java.lang.Thread.run(Thread.java:745)
00:00:09.614 	at ......remote call to Channel to /10.130.221.14(Native Method)
00:00:09.614 	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1435)
00:00:09.614 	at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
00:00:09.614 	at hudson.remoting.Channel.call(Channel.java:795)
00:00:09.614 	at jenkins.plugins.nodejs.tools.NodeJSInstallation.getExecutable(NodeJSInstallation.java:87)
00:00:09.615 	at jenkins.plugins.nodejs.NodeJSCommandInterpreter.perform(NodeJSCommandInterpreter.java:96)
00:00:09.615 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
00:00:09.615 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
00:00:09.615 	at hudson.model.Build$BuildExecution.build(Build.java:205)
00:00:09.616 	at hudson.model.Build$BuildExecution.doRun(Build.java:162)
00:00:09.616 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
00:00:09.616 	at hudson.model.Run.execute(Run.java:1728)
00:00:09.616 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
00:00:09.616 	at hudson.model.ResourceController.execute(ResourceController.java:98)
00:00:09.616 	at hudson.model.Executor.run(Executor.java:404)
00:00:09.617 Build step 'Execute NodeJS script' marked build as failure

Made a separate job that just has the one npm step with nothing in it (or something simple like 2+2), in this job I only get the above Stacktrace and not the npm install -g error.

My jenkins home folder (on the node) does not have anything resembling the xml file you requested.
Tool config screenshot is attached.

regs@akom.net (JIRA)

unread,
Feb 10, 2017, 6:25:01 PM2/10/17
to jenkinsc...@googlegroups.com
Alexander Komarov edited a comment on Bug JENKINS-41876
I'm seeing the same thing, confirmed no spaces in global npm packages field, saved again.


{noformat}
{noformat}

Made a separate job that just has the one npm step with nothing in it (or something simple like 2+2), in this job I only get the above Stacktrace and not the *npm install -g* error.


My jenkins home folder (on the node) does not have anything resembling the xml file you requested.
Tool config screenshot is attached.

!Screenshot_2017-02-10_16-21-49.png|thumbnail!

BTW: this worked with 0.2.1, I haven't changed the job or tool config after upgrading just this plugin.

david.weber.schenker@gmail.com (JIRA)

unread,
Feb 10, 2017, 6:41:02 PM2/10/17
to jenkinsc...@googlegroups.com

I can confirm that my configuration is clean. So the xml node for the global modules is not existing in my plugin xml config.

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2017, 8:15:01 PM2/10/17
to jenkinsc...@googlegroups.com
Nikolas Falco updated an issue
 
Change By: Nikolas Falco
Attachment: jenkins.plugins.nodejs.tools.NodeJSInstallation.xml

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2017, 8:23:01 PM2/10/17
to jenkinsc...@googlegroups.com
Nikolas Falco updated an issue
Change By: Nikolas Falco
Attachment: config.xml

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2017, 8:36:01 PM2/10/17
to jenkinsc...@googlegroups.com
Nikolas Falco commented on Bug JENKINS-41876
 
Re: Not respecting configuration in regards of global modules

I can not reproduce this issue.
I have try with a clean Jenkins 1.625.3 / 2.32.2 / 2.44 installation (MacOS)

  1. for Jenkins 2.x installation I had select only the NodeJS 1.0.1 plugin to install
  2. after it completes setup I configure a new NodeJS installation in "Global Tool Configuration" page like in screenshot. Then save, the file jenkins.plugins.nodejs.tools.NodeJSInstallation.xml have to appear under jenkins home folder (master node, not slave). If the file does not exist means no installation have been saved.
    Maybe you could have nodejs.xml file, this because you have 0.2.x version installed not 1.0.x.
  3. I create a new Freestyle job named test1
  4. I add a build step "Execute NodeJS script";
    • selecting nodejs-4-latest as installation
    • this as script content 
      console.log(2+2)
    • leave npmrc default

This is the job configuration file config.xml

Follow the console ouput (the same for all Jenkins version):

Started by user anonymous
Building in workspace /Users/nikolasfalco/git/nodejs-plugin/work/workspace/test1
Unpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-darwin-x64.tar.gz to /Users/nikolasfalco/git/nodejs-plugin/work/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on Jenkins
[test1] $ /Users/nikolasfalco/git/nodejs-plugin/work/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin/node /var/folders/jq/2l9t7bw1103_jjyv9rzk7kcr0000gn/T/hudson7746704401481264781.js
4
Finished: SUCCESS

Please to understand the issue provide me:

  1. the job config.xml file
  2. tools installation jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file
  3. Alexander Komarov provide your operative system
  4. if job runs on a slave node or master

scm_issue_link@java.net (JIRA)

unread,
Feb 10, 2017, 10:36:01 PM2/10/17
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Nikolas Falco
Path:
src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java
http://jenkins-ci.org/commit/nodejs-plugin/e092acdca13d41e5065743289d0b986e652e6fe8
Log:
JENKINS-41876 Check if global package value is blank instead null why after persistence migration value could not be null if in previous 0.2.x version value was spaces. XStream during de-serialisation does not instantiate object by its constructor, this means npmPackages value will empty (instead null) till a save is performed in configuration page.

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2017, 10:36:02 PM2/10/17
to jenkinsc...@googlegroups.com
Nikolas Falco assigned an issue to Nikolas Falco
 
Change By: Nikolas Falco
Assignee: Nikolas Falco

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2017, 10:36:02 PM2/10/17
to jenkinsc...@googlegroups.com
Nikolas Falco started work on Bug JENKINS-41876
 
Change By: Nikolas Falco
Status: Open In Progress

regs@akom.net (JIRA)

unread,
Feb 11, 2017, 12:10:04 PM2/11/17
to jenkinsc...@googlegroups.com
Alexander Komarov updated an issue
Change By: Alexander Komarov
Attachment: config.xml

regs@akom.net (JIRA)

unread,
Feb 11, 2017, 12:18:01 PM2/11/17
to jenkinsc...@googlegroups.com
Alexander Komarov commented on Bug JENKINS-41876
 
Re: Not respecting configuration in regards of global modules

Answers regarding my configuration:

  1. OS: Centos 6.8 on master.
  2. Centos 7.0 on docker slaves (both Docker kernel and docker image).
  3. I still don't see a jenkins.plugins.nodejs.tools.NodeJSInstallation.xml on either slaves or master.
  4. Attaching my job config.xml:
  5. config.xml

Here are all the XML files I can find:

[root@4b45a776e3ee /]# find  / -xdev -name '*.xml' | grep -i node | grep tool
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/aosp_manifest.xml
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-03.xml
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-04.xml
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/aosp_manifest.xml
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-03.xml
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-04.xml

regs@akom.net (JIRA)

unread,
Feb 11, 2017, 12:45:02 PM2/11/17
to jenkinsc...@googlegroups.com

Nikolas Falco I tried your branch (feature/JENKINS-41876) and I get a different failure:

FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"


Build step 'Execute NodeJS script' marked build as failure

I changed the job so it wipes out the installation preemptively, then shows the contents. Here is the output.

[test-npm] $ /bin/sh -xe /tmp/hudson9048595079863518522.sh
+ rm -rf /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation
Unpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz to /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on BigMemory-Swarm-34234051b8dd
FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"
Build step 'Execute NodeJS script' marked build as failure
Performing Post build task...
Match found for : : True
Logical operation result is TRUE
Running script  : ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest
[test-npm] $ /bin/sh -xe /tmp/hudson5550127812103304562.sh
+ ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest:
total 996
-rwxrwxr-x 1 root root 938291 Jan 31 21:05 CHANGELOG.md
-rwxrwxr-x 1 root root  54656 Jan 31 21:05 LICENSE
-rwxrwxr-x 1 root root  17439 Jan 31 21:05 README.md
drwxr-xr-x 2 root root     27 Feb 11 17:42 bin
drwxr-xr-x 3 root root     17 Feb 11 17:42 include
drwxr-xr-x 3 root root     25 Feb 11 17:42 lib
drwxr-xr-x 5 root root     42 Feb 11 17:42 share

/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin:
total 24252
-rwxrwxr-x 1 root root 24830187 Jan 31 21:05 node
lrwxrwxrwx 1 root root       38 Feb 11 17:42 npm -> ../lib/node_modules/npm/bin/npm-cli.js

regs@akom.net (JIRA)

unread,
Feb 11, 2017, 12:49:02 PM2/11/17
to jenkinsc...@googlegroups.com
Alexander Komarov edited a comment on Bug JENKINS-41876
[~nfalco] I tried your branch (feature/JENKINS-41876) and I get a different failure:


FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"
Build step 'Execute NodeJS script' marked build as failure

I changed the job so it wipes out the installation preemptively, then shows the contents.  Here is the output.

{noformat}


[test-npm] $ /bin/sh -xe /tmp/hudson9048595079863518522.sh
+ rm -rf /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation
Unpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz to /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on BigMemory-Swarm-34234051b8dd
FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"
Build step 'Execute NodeJS script' marked build as failure
Performing Post build task...
Match found for : : True
Logical operation result is TRUE
Running script  : ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest
[test-npm] $ /bin/sh -xe /tmp/hudson5550127812103304562.sh
+ ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest
/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest:
total 996
-rwxrwxr-x 1 root root 938291 Jan 31 21:05 CHANGELOG.md
-rwxrwxr-x 1 root root  54656 Jan 31 21:05 LICENSE
-rwxrwxr-x 1 root root  17439 Jan 31 21:05 README.md
drwxr-xr-x 2 root root     27 Feb 11 17:42 bin
drwxr-xr-x 3 root root     17 Feb 11 17:42 include
drwxr-xr-x 3 root root     25 Feb 11 17:42 lib
drwxr-xr-x 5 root root     42 Feb 11 17:42 share

/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin:
total 24252
-rwxrwxr-x 1 root root 24830187 Jan 31 21:05 node
lrwxrwxrwx 1 root root       38 Feb 11 17:42 npm -> ../lib/node_modules/npm/bin/npm-cli.js
{noformat}

Just for fun I also tried it outside of Docker, with a normal linux slave: same behavior.

scm_issue_link@java.net (JIRA)

unread,
Feb 12, 2017, 6:30:03 AM2/12/17
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Nikolas Falco
Path:
src/test/java/jenkins/plugins/nodejs/tools/NodeJSInstallationTest.java
http://jenkins-ci.org/commit/nodejs-plugin/0c223513bc354ada0711868b556ed84f7c8787b7
Log:
JENKINS-41876 Add test case.

scm_issue_link@java.net (JIRA)

unread,
Feb 12, 2017, 6:33:01 AM2/12/17
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Nikolas Falco
Path:

pom.xml
src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java
src/test/java/jenkins/plugins/nodejs/NodeJSInstallerTest.java
http://jenkins-ci.org/commit/nodejs-plugin/652e9f4884995dcf7a932a04d4949a7c0f71162a


Log:
JENKINS-41876 Add test case.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 6:44:01 AM2/12/17
to jenkinsc...@googlegroups.com

Alexander Komarov let me try to reproduce your setup (master linux -> slave linux) and your job/global tool configuration.

Just to clarify if you do not have jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file in the home of master jenkins (near the others persistence file for Maven/Ant etc etc) when you reboot the NodeJS tool configuration is lost. Your it's a very unreproducible strange case.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 6:45:01 AM2/12/17
to jenkinsc...@googlegroups.com
Nikolas Falco edited a comment on Bug JENKINS-41876
[~akom] let me try to reproduce your setup (master linux -> slave linux) and your job/global tool configuration.


Just to clarify if you do not have jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file in the home of master jenkins (near the others persistence file for Maven/Ant etc etc) when you reboot the NodeJS tool configuration is lost. Your it's a very unreproducible strange case.


Anyway the case of npm install -g with empty list of packages was fixed in master.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 6:53:01 AM2/12/17
to jenkinsc...@googlegroups.com
Nikolas Falco edited a comment on Bug JENKINS-41876
[~akom] let me try to reproduce your setup setupwithout docker (master linux -> slave linux) and your job/global tool configuration.


Just to clarify if you do not have jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file in the home of master jenkins (near the others persistence file for Maven/Ant etc etc) when you reboot the NodeJS tool configuration is lost. Your it's a very unreproducible strange case.

Anyway the case of npm install -g with empty list of packages was fixed in master.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 7:10:01 AM2/12/17
to jenkinsc...@googlegroups.com
Nikolas Falco edited a comment on Bug JENKINS-41876
[~akom] let me try to reproduce your setup, without docker (master linux -> slave linux) and your job/global tool configuration.

Just to clarify if you do not have jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file in the home of master jenkins near the others persistence file:
* disk-usage ( -> hudson.plugins.disk_usage.DiskUsageProperty.xml )
* Maven -> hudson.tasks.Maven.xml
* Ant ( -> hudson.tasks.Ant.xml )

If you reboot Jenkins instance NodeJS global tool configuration will be lost (you have to redefine them). Your it's a very unreproducible strange case.


Anyway the case of npm install -g with empty list of packages was fixed in master.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 7:10:02 AM2/12/17
to jenkinsc...@googlegroups.com
Nikolas Falco edited a comment on Bug JENKINS-41876
[~akom] let me try to reproduce your setupwithout setup, without docker (master linux -> slave linux) and your job/global tool configuration.

Just to clarify if you do not have jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file in the home of master jenkins ( near the others persistence file for :
* disk-usage (hudson.plugins.disk_usage.DiskUsageProperty.xml)
* Maven / hudson.tasks.Maven.xml
* Ant etc etc (hudson.tasks.Ant.xml ) when
If you reboot the Jenkins instance NodeJS global tool configuration is will be lost (you have to redefine them) . Your it's a very unreproducible strange case.


Anyway the case of npm install -g with empty list of packages was fixed in master.

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 8:34:01 AM2/12/17
to jenkinsc...@googlegroups.com

I got it.

A regression in master code due rework of JENKINS-40624 cause command not found exception in case of execution master -> slave

nfalco79@hotmail.com (JIRA)

unread,
Feb 12, 2017, 2:06:02 PM2/12/17
to jenkinsc...@googlegroups.com
Nikolas Falco closed an issue as Fixed
 

Fix in master
Change By: Nikolas Falco
Status: In Progress Closed
Resolution: Fixed

regs@akom.net (JIRA)

unread,
Feb 12, 2017, 5:44:01 PM2/12/17
to jenkinsc...@googlegroups.com

scm_issue_link@java.net (JIRA)

unread,
Feb 13, 2017, 1:41:04 PM2/13/17
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Nikolas Falco
Path:
src/test/java/jenkins/plugins/nodejs/NodeJSInstallerTest.java
http://jenkins-ci.org/commit/nodejs-plugin/f0b500baeaa7cee21c1c519c951f9a26a3564655
Log:
JENKINS-41876 Replaced with original correct test.
Reply all
Reply to author
Forward
0 new messages