Another problem is that certain aspects of the job continue to behave as if it 
is still running on Linux.
As shown below, the job attempts to create a sym-link--even though it is now 
running on Windows (from the Console text):
Started by user anonymous
ln builds\lastSuccessfulBuild D:\Jenkins\jobs\testjob\lastSuccessful failed
hudson.util.jna.WinIOException: Failed to create a symlink 
D:\Jenkins\jobs\testjob\lastSuccessful to builds\lastSuccessfulBuild 
error=183:Cannot create a file when that file already exists
        at 
hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:92)
        at hudson.Util.createSymlink(Util.java:1084)
        at hudson.model.Run.createSymlink(Run.java:1784)
        at hudson.model.Run.updateSymlinks(Run.java:1765)
        at hudson.model.Run.execute(Run.java:1677)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:230)
ln builds\lastStableBuild D:\Jenkins\jobs\testjob\lastStable failed



On Monday, March 31, 2014 3:53:16 PM UTC-4, Steve K wrote:
>
> Thanks Daniel,
>
> I was concerned about how Windows was going to handle the Linux sym-links.
> When I copied a job from the Linux disk (shared via Samba) to Windows, 
> Windows turned those sym-links into "real" files and directories.
> That probably means I'll have a lot of redundant data.
> The job appears to be preserved though--except for the "Job Config 
> History".  That's probably a separate copy.
>
> I'm wondering if there are any other "gotchas".
>
> Regards,
>
> Steve K.
>
> On Monday, March 31, 2014 2:53:43 PM UTC-4, Daniel Beck wrote:
>>
>> It should suffice to just copy the files over to another Jenkins 
>> instance, and restart it. Make sure all plugins used in the job are 
>> available in compatible versions. 
>>
>> Since you're switching OSes, you might need to delete the symbolic links, 
>> e.g. build number -> build ID links in the 'builds' directory, or the last* 
>> links in the job directory, and have Jenkins recreate them. 
>>
>> On 31.03.2014, at 20:24, Steve K <[email protected]> wrote: 
>>
>> > Hello, 
>> > 
>> > I'd like to bring along all of the job's history. 
>> > Is there any way I can move a job from a Linux master to a Windows 
>> master? 
>> > The Linux master is being decommissioned. 
>> > 
>> > Thanks in advance. 
>> > 
>> > Steve K. 
>> > 
>> > 
>> > -- 
>> > 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 [email protected]. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to