Open easterism opened 9 years ago
+1
Workaround: You could login as the same user as phpci runs, do a svn co https://example.com/repo and enter user name and password and let svn cache it in the ~/.subversion
directory
I didn't have any way to check svn or to help you. Did you search on the other svn issues if maybe someone has the same issue and fixed it?
If you have any idea to fix it, feel free to create a pull request
Did not yet have time for a PR. But SVN has parameters --username and --password - so it should be just possible to specify those parameters.
That's what i said. Just add username and password fields as alternative to certificate authorization.
I'd also like to see username and password field as an alternative to certificate authorization.
Hi. Could you please make some advise about SVN. I tried to use it on self-hosted PHPCI on Debian. My SVN server is another Debian machine. So I use SSH keys. The public RSA key inside /root/.ssh Also I copied the private RSA to my PHPCI project. But after build launched I received "authorization failed: Could not authenticate to server: rejected Basic challenge". P.S. I think you can add another access option to the SVN. Just user name and password. It's fastest way, especially if you havn't SSH pairs