Yeah, this is a show stopper for us . . . I cannot have Jenkins shutting itself down.
I thought at first perhaps the issue was related to using a UNC path \\<server>\<share>\somepath, but mounting the share as a network drive and using x:\somepath didn't help.
Account HAS ACCESS to this location, I've browsed there as that user, created and deleted a file. (Jenkins itself has yet to write so much as one byte in the specified directory).
First four settings: X:\Users\hjenkins\March-Web, 30 0 * * *, 10 * * * *, 10
All other settings are blank or unchecked.
Note this works fine for me at home no issues . . . the biggest difference at work is that the number of jobs is of course much bigger (over 100) and the number of plugins.
Just in case it is a plugin interaction issue . . . plugin info below:
Maven 2 Project Plugin
Jenkin's Maven 2 project type
Warning: This plugin is built for Jenkins 1.452 or newer. It may or may not work in your Jenkins.
Static Code Analysis Plug-ins
This plug-in provides utilities for the static code analysis plug-ins.
This plugin generates the trend report for compiler warnings in the console log or in log files.
Changes Hudson to use green balls instead of blue for successful builds
Integrates Jenkins with Perforce SCM Repositories.
1.3.9 1.3.8-SNAPSHOT (private-01/23/2012 01:19-gregf)
This bundled plugin integrates Jenkins with CVS version control system.
This plugin lets you search keywords in the files you specified and use that to downgrade a "successful" build to be unstable or a failure.
This plugin adds the Subversion support (via SVNKit) to Jenkins.
This plugin adds the ability to directly execute Groovy code.
Scriptler allows you to store/edit groovy scripts and execute it on any of the slaves/nodes... no need for copy paste groovy code anymore.