[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows

NodeJS tool installation fails on Windows

Issue Type:	Bug
Assignee:	Nikolas Falco
Attachments:	image-2019-10-21-13-07-02-606.png
Components:	nodejs-plugin
Created:	2019-10-21 12:11
Environment:	Windows Server 2019 (OS Build 17763.678)
Labels:	windows
Priority:	Major
Reporter:	James Howe

Tool installation on a Windows node fails for some reason at this rename:

 
                                                                Unpacking [https://nodejs.org/dist/v10.16.3/node-v10.16.3-win-x64.zip] to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10 on devops-test3-vm

java.io.IOException: Failed to rename C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64 to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64.__rename
	at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2171)
	at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2159)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
 
                                                            

Config:

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

regs@akom.net (JIRA)

unread,

Oct 23, 2019, 8:49:13 AM10/23/19

to jenkinsc...@googlegroups.com

Alexander Komarov commented on

I can confirm that this also happens exactly this way with nodejs 7, and only on Windows Server 2019. This does not happen on 2008, 2012, 2016 or Windows 10 (I have a matrix job with all of the above).

Deleting tools\jenkins.plugins.nodejs.tools.NodeJSInstallation did not help.

regs@akom.net (JIRA)

unread,

Oct 23, 2019, 8:51:02 AM10/23/19

to jenkinsc...@googlegroups.com

Alexander Komarov edited a comment on

I can confirm that this also happens exactly this way with *nodejs 7*, and *only* on *Windows Server 2019*. This does not happen on 2008, 2012, 2016 or Windows 10 (I have a matrix job with all of the above).

Deleting *tools\jenkins.plugins.nodejs.tools.NodeJSInstallation* did not help.

Environment:
* Jenkins 2.174
* NodeJS Plugin 1.2.7

regs@akom.net (JIRA)

unread,

Oct 23, 2019, 8:54:02 AM10/23/19

to jenkinsc...@googlegroups.com

Alexander Komarov edited a comment on

I can confirm that this also happens exactly this way with *nodejs 7*, and *only* on *Windows Server 2019* slaves . This does not happen on 2008, 2012, 2016 or Windows 10 (I have a matrix job with all of the above).

Deleting *tools\jenkins.plugins.nodejs.tools.NodeJSInstallation* did not help.

Environment:
* Jenkins 2.174
* NodeJS Plugin 1.2.7

nfalco79@hotmail.com (JIRA)

unread,

Oct 23, 2019, 12:52:03 PM10/23/19

to jenkinsc...@googlegroups.com

Nikolas Falco commented on

Unfortunately I do not have any windows server 2019 to try.

regs@akom.net (JIRA)

unread,

Oct 23, 2019, 7:25:02 PM10/23/19

to jenkinsc...@googlegroups.com

Alexander Komarov commented on

Nikolas Falco I'd be happy to do some investigation and run some samples if you can point me in the right direction. Neither maven nor groovy auto-installs have this issue so the installation must be done differently (ie not using MoveAllChildrenTo?)

james@howeswho.co.uk (JIRA)

unread,

Oct 24, 2019, 6:43:04 AM10/24/19

to jenkinsc...@googlegroups.com

James Howe commented on

My guess was something to do with the old MAX_PATH limit, but if it's only Windows 2019 that's more odd.