gt; That means it will never hang waiting for a prompt. Instead, it will fail,
> and the output will tell you what happened.
>
> Matthew
>
>
>
> *From:* Juan Pablo Hernandez Vogt [mailto:j...@open-engineering.com]
> *Sent:* 11 June 2014 13:43
> *To:* jenkinsci-users@goo
:35:56 UTC+1, Juan Pablo Hernandez Vogt a écrit :
>
> Le mercredi 11 juin 2014 16:01:24 UTC+1, Eric Pyle a écrit :
>>
>> By default a Windows service runs as the Local User account, which has
>> no access to network resources. Try configuring the service to run as a
losed unexpectedly
b) Starting Pagent.exe and trying again works!
So, what I have here is that my service, launched as my user, does not
"see" my Pagent.exe process.
Best regards,
JP
On 6/11/2014 8:42 AM, Juan Pablo Hernandez Vogt wrote:
>
> Hello,
>
> I tried to fin
Hello,
I tried to find an answer in the list but I did not find what is wrong.
Probably is a stupid thing...
The job only execute a command *svn update* in my Windows 8.1 machine:
a) If I start the client from JNLP file, the job is executed.
b) If I install it as service, it holds waiting... w
Hello,
I've just installed v1.555 in a CentOS 6.5. I added:
+ WinXP node
+ Win8.1 node
+ Job to make a "dir C:\"
I start the slave from JNPL and execute the job correctly on both nodes.
When I select Jenkins>Nodes>NODID>Disconnect the following error message
raises [1]. The jenkins slave did no
