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 wrote:
>
> > As shown below, the job attempts to create
On 31.03.2014, at 22:13, Steve K 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
e 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 wrote:
>>
>> > Hello,
>
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 wrote:
>
> > Hello,
> >
> > I'd like to bring along all of the job's history.
> > Is there any w
'builds' directory, or the last* links in
the job directory, and have Jenkins recreate them.
On 31.03.2014, at 20:24, Steve K 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 Win
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
