Linards L edited a comment on Bug JENKINS-20630

@cforce,

I will do it now, but it will not be valid test anymore because once I reverted to v1.529, I updated plugins. So it might work now, but it does not cover the issue I had earlier - crash after second reboot ( after plugins update ).

Test scenarion:

1. Up and running jenkins v1.529 with master and three slaves; All slaves offline;
2. Plugins - all updated ( from my last attempt ( see date of my previous comment here ));
3. Creating a slave ; installing as windows service ; starting it - up and running;
3.1 Updating java to 1.7u45 ;
4. Performing automatic upgrade with one job running and one in queue ; waiting till it finishes;

Resulting in error from console before returning

Finished: SUCCESS

in console:

ln builds\lastStableBuild c:\jenkins_master\jobs\trunk-build\lastStable failed
java.nio.file.DirectoryNotEmptyException: c:\jenkins_master\jobs\trunk-ExportDlls\lastStable
	at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
	at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)
	at java.nio.file.Files.deleteIfExists(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at hudson.Util.createSymlinkJava7(Util.java:1146)
	at hudson.Util.createSymlink(Util.java:1070)
	at hudson.model.AbstractBuild.createSymlink(AbstractBuild.java:494)
	at hudson.model.AbstractBuild.access$700(AbstractBuild.java:105)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729)
	at hudson.model.Run.execute(Run.java:1628)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:247)

5. Rebooting jenkins;
6. Updating plugins, if available.
7. Checking result...

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to