The paths to our svn repos are
ssh://192.168.8.100//var/hg/some_repo
I've tried combinations of
svn+ssh://192.168.8.100//var/hg/some_repo
svn+ssh://username@192.168.8.100//var/hg/some_repo
with basic authentications with
Forced HTTP Auth checked
Forced HTTP Auth unchecked
and absolute and relative paths to my id_rsa file that has no Protocol pass phrase. Every permutation gives me the error
svn: E215000: Credential data unavailable
I've tried looking for a definitive example for my environment but so far haven't found one. What steps do I need to take to add our repository?
Thanks for reading.
I won't be surprised if this is pilot error, but as of now I'm still not finding the combination that will work for us. Should I try to find some other svn solution?
This is how I did it just now:
That worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
I've got the exact same problem: using the svn+ssh:// protocol causes the "svn: E215000: Credential data unavailable" error, no matter what other data I supply in the username/password/keyfile.
@Karl-König Königsson which version of the Subversion ALM plugin are you using?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am right now on 9.0.3, but since my answer is about a year old I can not tell for sure which version I was running then. On the other hand, I have been rather lazy about updating the plugins so it might well be that 9.0.3 is the one I had.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok, I'm trying to get things running with 9.0.9. Thanks for the info!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.