Thanks again Daniel. Getting rid of the sym-links prior to copying over to Windows does seem to make the target system happier. Cheers!
On Monday, March 31, 2014 5:34:29 PM UTC-4, Daniel Beck wrote: > > > On 31.03.2014, at 22:13, Steve K <steve.kerxha...@carestream.com> wrote: > > > As shown below, the job attempts to create a sym-link--even though it is > now running on Windows (from the Console text): > > Actually, Windows/NTFS have symbolic links (run 'mklink /?' in cmd). > AFAIK, Jenkins uses them if possible. > > I'd try to copy the job dir still on Linux, run `find > path/to/copied/jobdir -type l -delete` to delete them, and copy only the > actual files/folders over to Windows afterwards to see what happens. > > > The job appears to be preserved though--except for the "Job Config > History". That's probably a separate copy. > > Probably in $JENKINS_HOME/config-history or similar. It's again only a > matter of copying the files over, might even be possible while Jenkins is > running. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
