Thanks! That seems to have done the trick.
On Wed, Dec 12, 2012 at 1:41 PM, Strausser, Barrett <
barrett.straus...@snapretail.com> wrote:
> Yeah just move the slave. You should be able to just do D:\JenkinsSlave in
> the node configuration.
>
>
> On Wed, Dec 12, 2012 at 3:26 PM, Bill Wonch wro
Yeah just move the slave. You should be able to just do D:\JenkinsSlave in
the node configuration.
On Wed, Dec 12, 2012 at 3:26 PM, Bill Wonch wrote:
> I probably could. I just used the jnlp method to create the slave but if
> another metthod works better, I'm open to it.
>
>
> On Wednesday, D
I probably could. I just used the jnlp method to create the slave but if
another metthod works better, I'm open to it.
On Wednesday, December 12, 2012 12:11:30 PM UTC-7, Bill Wonch wrote:
>
> Hi everyone -
>
> I just created my first slave node, and I get the following message when I
> start it
Why don't you install the slave onto D:\
You are asking for headaches in the situation you are trying to pull.
What does it say in your event log? Or in the slave logs?
On Wed, Dec 12, 2012 at 2:11 PM, Bill Wonch wrote:
> Hi everyone -
>
> I just created my first slave node, and I get the fol
Hi everyone -
I just created my first slave node, and I get the following message when I
start it:
Disk space is too low. Only 0.982GB left on C:\WINDOWS\Temp.
I've done some research, and our JVMs are configured in such a way that C:
is very small, so I changed the value of java.io.tmpdir to
