I have the same question regarding Windows slaves, specifically in Amazon E2.
Our Jenkins master is running on a Windows server inside the company firewall, not accessible from outside. I can create build machines on E2 with public IP addresses. The question is how to get them to talk. I have gotten OpenVPN 2.2 working on a couple of local machines. It wasn’t too hard (after I got it working J). It seems that the machine that has the public IP would have to be configured as the OpenVPN server so that a hidden machine could connect to it. But that would mean that the Jenkins server would be configured as an OpenVPN client. I can see this working for one cloud slave, but not for 20. Tin that case 20 instances of OpenVPN client would need to run on the server. Right? Any ideas on this? Thanks Richard On Tuesday, August 28, 2012 10:13:31 AM UTC-7, LesMikesell wrote: > On Tue, Aug 28, 2012 at 11:42 AM, Jerome Lacoste > <jerome....@gmail.com <javascript:>> wrote: > > Hei, > > > > As anyone tried using Windows Azure (or similar) to setup a Windows > slave in > > the cloud ? > > > > I am not that comfortable having a cloud computer connect into my > company > > network. I would prefer it the other way around... > > And Windows Azure Connect (for VPN) seems to require a Windows network > to > > connect to and I don't have any... > > > > I don't know anything about azure, but OpenVPN should work as long as > at least one end has a public address or can use port-forwarding to > reach the other end. It is fairly nat-friendly and only needs one > udp or tcp port. > > -- > Les Mikesell > lesmi...@gmail.com <javascript:> >
