[Buildbot-devel] buildbot slave on windows hangs on mercurial checkout

[Marcus Lindblom]

Christian Scholz wrote:
> 
> Hi!
> 
>> Christian Scholz wrote:
>>> Hi!
>>> I am just doing my first steps with buildbot and so far it looks  
>>> like a great tool. I am having a problem under windows though where  
>>> I am trying to do a mercurial checkout from an SSH server.
>>> The account under which buildbot is running has the following setup:
>>> - TortoiseHG installed
>>> - buildbot under Python 2.5 - ssh key pair generated via puttygen
>>> - public key copied to server into the hg account
>>> - putty is working and I once accpepted the host key
>>> - installed pageant and added the private key to it
>>> - putty is not asking for the password anymore (in fact this key  
>>> has no password right now)
>>> Then I added a step to clone a mercurial repository via ssh:// 
>>> hg at host/
>>> repourl but all it's doing is that the step is hanging forever  
>>> until the timeout kills it after 1200 seconds.
>>> The logfile only shows the initial shell command with the  
>>> environment and when I copy the command line over to the windows  
>>> machine (a VM) and run it manually in a shell it succeeds.
>> Dummy-check: are you running buildbot under the same user as the  
>> shell, with the same priviliges?
> 
> I think so. Of course with windows I am never sure what I am doing but  
> basically I run the hg command manually in the same shell as I run  
> "buildbot start slave". It's also the Administrator and in the log  
> output on the master I also see Administrator as the user in the  
> command's environment.

Sounds ok. Hm.

>>> Does anybody know what the problem might be or how I can debug this  
>>> further?
>> Not really. We've used anonymous http-checkouts for hg/buildbot here  
>> so far, so I've no experience with SSH there, yet.
> 
> Too bad.. I might end up doing a samba export of that repo but that's  
> not the ideal solution. Or maybe a password protected HTTP checkout  
> might work as well.

For devs, we use ssh-keys without passwords and specify a path to the 
local key directly in the user's .hgrc/mercurial.ini on the ssh setting, 
using tortoiseplink.exe. You might have some success going by that 
route, instead of putty/pageant (which I've never tried... sounds like a 
nice setup to get some password protection in there as well... :).

Cheers,
/Marcus