I've not had this problem that I remember.  Once I got the slave service 
setup via the web link, I've not seen issues.  I think that I did have 
issues when I let Jenkins setup the service via remote management though. 
 That would have been early on in my Jenkins trials.  The service wouldn't 
consistently start up and went down and I couldn't get it to come back up 
without a VM restart.

For the ssh, I thought about this and thought about using the ssh daemon in 
Cygwin, but I wasn't sure how our existing batch scripts would operate 
running through the ssh daemon, and JNLP was running fine so I didn't 
pursue it.  I guess the batch scripts should be fine, but haven't thought 
it through or tested it.  I do run Cygwin on my WinXP VMs w/ the ssh 
daemon, so I could test it at some point if JNLP starts acting up.

If I test it at some point I'll comment back here.  If you end up running a 
ssh solution, do share your results.

Sorry I'm not more help.


On Monday, July 29, 2013 4:05:44 PM UTC-4, David Gayman wrote:
>
> I tried this procedure including running under the correct user, and it 
> works, but there have been reliability issues. Occasionally the service has 
> failed to start for no apparent reason. This has not happened since I 
> uninstalled (sc delete jenkinsservice-C__jenkins), and re-installed the 
> service.
>
> Have you had similar reliability issues?
>
> The second part of my question is how to configure ssh. I see it as way 
> more reliable, if configured properly. If a user cannot get JNLP to work 
> for some reason, they can't fall back to the ssh option.
>
>
>
>
> On Mon, Jul 29, 2013 at 10:47 AM, Shannon Kerr 
> <shanno...@gmail.com<javascript:>
> > wrote:
>
>> I run multiple Windows XP VMs with no issues.  I set them up using "Java 
>> Web Start" and once they are started click on "File" in the pop up window 
>> to enable them as a service on that Windows XP machine (for me they are 
>> VMs).  Once I set them up as a service, I change the account that the 
>> service runs under (I needed this, but you may not) by going to "Services" 
>> on the Win XP VM and restarting the service.  It works great.  Have you 
>> tried this and you are not getting it working?
>>
>>
>>
>> On Sunday, July 28, 2013 8:28:07 PM UTC-4, qbd...@vt.edu wrote:
>>>
>>> I am having a hard time connecting a windows XP slave to a jenkins build 
>>> system. Builds currently take place on linux, unix, and windows 7.
>>>
>>> I successfully installed the JNLP option as a service, as is working for 
>>> windows 7. However it is unreliable, sometimes won't start, and after a day 
>>> or two it disconnects from the system (only xp has this problem).
>>>
>>> ssh to my linux slaves works great! Why can't ssh to windows slave work? 
>>> It seems to be the most reliable. But how can I configure ssh to connect to 
>>> the WINDOWS command prompt, not EMULATED LINUX shell? I am using the cygwin 
>>> ssh server, and there don't seem to be many other free options.
>>>
>>> Alternatively, I've considered how to run a command in cygwin that would 
>>> expose the underlying windows command-line environment, but I don't know 
>>> enough about windows to make "system calls" from within cygwin, much less 
>>> what these calls need to be.
>>>
>>> If I had enough time I would consider writing my own ssh server, 
>>> correctly so none of these issues exist.
>>>
>>  -- 
>> 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/jM-FgGgrBXo/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-use...@googlegroups.com <javascript:>.
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to