Jenkins can't connect to my Windows dumb slave

[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?

[Deniz Zoeteman]

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:

[Vincent Latombe]

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 <dkzoe...@gmail.com>

--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Deniz Zoeteman]

Moving from 1.547 to 1.546 fixed the issue indeed. Thank you for your help!

-Deniz

2014/1/21 Vincent Latombe <vincent...@gmail.com>

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/Q2jS5-6Zd9c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[Vincent Latombe]

So it matches the extraction of windows slave to a plugin (https://github.com/jenkinsci/jenkins/commit/2669e4a86d72f2d8b67417812db8f52aa487f3de). I guess something has gone wrong in the process...