 |
History
| Log In
|
|
|
|
Jason,
Thanks for the reply. I did think it was odd that some combinations gave one error (indicating successful contact with the SVN server) and some seemed to not be able to connect at all. Just to clarify...because the info presented confused me. If a normal svn command for me issued in a console is: svn+ssh://mblewett@mail.digideal.com/home/svn/repository/DigiFlash/Branches/DragonBacc_CV_GLI how does that translate into the SCM config tab in Pulse? Do I enter that entire string into the URL field, or do I strip off the 'mblewett@' and enter the mblewett in the username field? It's not clear to me. I will try to just run a build regardless of the outcome of the SCM check on the config and report back the results. Hi Mark,
> Do I enter that entire string into the URL field, or do I strip off the 'mblewett@' and enter the mblewett in the username field? You do the latter; i.e. in the url tab enter: svn+ssh://mail.digideal.com/home/svn/repository/DigiFlash/Branches/DragonBacc_CV_GLI then enter your username and password in the fields provided. Currently we don't support adding the credentials in the URL when a password is required. Jason-
We don't use a password, just a username and a private key. So to setup for this config I'd enter URL: svn+ssh://mail.digideal.com/home/svn/repository/DigiFlash/Branches/DragonBacc_CV_GLI username: mblewett private key file: /usr/mblewett/.ssh/id_dsa Is this correct? Hi Mark,
Ah sorry - I forgot you were using a key file. What you have suggested is exactly correct: enter the URL, username and private key file. You will also then need to restart Pulse as I explain below. Also: I have some more to report. I have now been able to reproduce the 'unable to contact pulse to run check' message. It occured when I entered the wrong credentials and after a significant delay. I believe what is happening is the backend is slow because of the bad credentials, and the client side (browser javascript) is timing out before the backend responds. To make matters worse, this failed authentication attempt appears to prevent future attempts from working even if you add the right credentials. SvnKit (the subversion library we are using) must be either caching the credentials or maybe has a bug around SSH connection pooling. I will look into the cause and hope to fix it for the next 2.0 build (2.0.9). For now, what you need to do is enter the credentials as in your last comment and then restart Pulse to clear out the failed authentication attempt that is blocking things. After that you should be able to run a build. Sorry for the inconvenience! I tracked this down to a bug in SvnKit, triggered by us using the APIs in a slightly unusual way. When switching to the idiomatic way, the bug is no longer triggered. Refer to change 4560 (in which I also upgraded to SvnKit 1.1.8). Thanks for finding this one Mark!
Glad I could help...and happy to confirm I wasn't configuring or doing something wrong in my setup to trigger this bug.
|
||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
SVN+SSH failing to connect
Thanks for the detailed report. The most interesting part is the message:
'unable to contact Pulse to run check '
This actually indicates that something went wrong between the web UI and the Pulse server when it was trying to setup a Subversion check. I doubt it got to the point where it was able to talk to your Subversion server at all in this case. The good news is that this means your configuration may work - it could just be a bug in the configuration checking UI code. To try this theory, would it be possible for you to just enter the configuration you expect to work (i.e. with the username and either a password or your private key file path) and try to run a build? This might get you started if we are lucky.
Returning to the check problem, I have had no luck repeating it here so far. We use svn+ssh ourselves, and trying under both FireFox 3 and IE7 seems to be OK. Clearly there is something different in your environment, I just can't figure out what. I wonder if your browser reports any javascript errors? Are you running Pulse using a custom context path by any chance?