Community
Participate
Working Groups
We have had to change all of the Virgo Repos to use https to check out sub-modules instead of the git protocol. This is as a result of new network security policy at VMware. Gits https protocol support is quite new so it may simply be a case of updating the Hudson plugin.
Copying in Hristo. This is why there is the current Virgo build mayhem on Hudson.
I found that on Windows https requires client side root certificates to be installed so the client can trust the server. More details and solution for Cygwin can be found here: http://stackoverflow.com/questions/3777075/https-github-access I suspect that the same may happen with Hudson too.
(In reply to comment #0) > We have had to change all of the Virgo Repos to use https to check out > sub-modules instead of the git protocol. This is as a result of new network > security policy at VMware. Gits https protocol support is quite new so it may > simply be a case of updating the Hudson plugin. I'm not sure I understand the relationship between VMWare's security policy and our Hudson plugin.
In short, we are now unable to use the port that the git protocol requires so we switched to https.
In more basic terms, we were forced to change Virgo to use https for its git submodules and now Hudson builds fail because Hudson isn't set up for https.
As part of another bug I've built and installed a new git RPM and made sure it provides HTTPS support. That should resolve the problem. -M.
Thanks Matt.
