I think I hit a similar issue while playing with latest core a few weeks back, so I think it is a regression at jenkins core level. I would recommend you to rollback to your previous jenkins core version (and probably raise an issue for this to track the regression)
Cheers, Vincent 2014/1/21 Deniz Zoeteman <[email protected]> > I should note that technically it can connect, but can't do anything much > it seems... it creates a jenkins folder on my C drive but that's it. > Op dinsdag 21 januari 2014 19:06:05 UTC+1 schreef Deniz Zoeteman: > >> I've set-up Jenkins for my Windows slave (I am running Jenkins under >> CentOS) with DCOM access (so Jenkins runs as service). >> This was working fine until I updated my CentOS set-up last night (incl. >> Jenkins), and now it can't seem to connect to my Windows node anymore.. it >> is stuck on "Checking if Java exists..." and /var/log/jenkins/jenkins.log >> just has an endless stream of "Attempting to reconnect windowsnode". >> >> Anyone any idea why this would be happening, and possibly how I could fix >> it? >> > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
