Ok, I'm going to knock this one on the head. Thanks for trying to help.
--
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...@googlegrou
On Fri, Oct 17, 2014 at 5:42 AM, Niksan wrote:
>> I mean, what is it that needs to use the full absolute path or even its
>> own working directory name?
>
> The four character path constraint.
>
> C:\\ This will work.
> C:\A\ This will not.
>
> This is a OS/Tools/Third party constraint,
> I mean, what is it that needs to use the full absolute path or even its
own working directory name?
The four character path constraint.
C:\\ This will work.
C:\A\ This will not.
This is a OS/Tools/Third party constraint, I don't see how not explicitly
setting a path will help, unle
On Thu, Oct 16, 2014 at 11:30 AM, Niksan wrote:
> That depends on what you mean by the rest of the path, the master suffers
> from the same issue,
I mean, what is it that needs to use the full absolute path or even
its own working directory name? What keep you from putting the
workspace anywhere
That depends on what you mean by the rest of the path, the master suffers
from the same issue, I suppose one way would be to have the master not
perform any builds and somehow leverage the
hudson.model.Slave.workspaceRoot token and omit the workspace override on
the job, if any of that makes an
On Thu, Oct 16, 2014 at 11:01 AM, Niksan wrote:
>
>> >No, if you run other jobs on that node they should be created as
>>
>
> Unfortunately, my jobs are path length volatile, currently four characters
> (I know, some constraints just suck). The jobs also have to be synchronous,
> as in I can have
> >No, if you run other jobs on that node they should be created as
>
>
Unfortunately, my jobs are path length volatile, currently four characters
(I know, some constraints just suck). The jobs also have to be synchronous,
as in I can have two of them running together on a singular machine. I
On Thu, Oct 16, 2014 at 9:46 AM, Niksan wrote:
> Oddly enough, if I set custom workspace and remote root both to C:\Chk this
> works as intended, but that limits one job per node. :/
>
No, if you run other jobs on that node they should be created as
C:\Chk\jobname\.
But that's probably not what y
Oddly enough, if I set custom workspace and remote root both to C:\Chk this
works as intended, but that limits one job per node. :/
--
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 i
So I have a job that sets to use a custom workspace with a directory of
C:\Chk, now, I'd like this directory to persist on a slave too on another
machine, but as you have to put a remote root directory you end up with the
slave creating folder along the lines of C:\C\Chk.
What's the correct set
10 matches
Mail list logo
