Contributions
- 3KViews0likes0Comments
Subversion GUI client configuration error
When i try to configure the v11 GUI Client using an existing SVN repository, i get the following error: Error: Could not create valid Subversion configuration based on current working directory: svn: E170013: Unable to connect to a repository at URL 'https://***.routematch.com:8443/svn/RouteMatch' svn: E215004: No more credentials or we tried too many times. Authentication failed From the command line, this process works fine. I can update and commit without error. Administrators-MacBook-Pro-5:database_29 dholmes$ svn info Path: . Working Copy Root Path: /Users/dholmes/Documents/Source/database_29 URL: https://***.routematch.com:8443/svn/RouteMatch/trunk/Database Relative URL: ^/trunk/Database Repository Root: https://***.routematch.com:8443/svn/RouteMatch How do i solve this?3.1KViews0likes3Comments- 2.2KViews1like0Comments
Re: Collaborator 9.2 Jira integration requires a paid 3rd party app
From http://support.smartbear.com/viewarticle/67412/ "Once FishEye integration with JIRA is established, ..." Now i get that i can create Jira from Collaborator without that but it reads like a third party piece of software is required tomake the integration complete.2.4KViews1like1CommentSVN Certificate issues with a trusted certificate
This was working on Monday and now i finally get someone to try it out and i am back to this. It works fine from the cmd line. notroot@RMDevTools01:~$ svn log https://subversion.routematch.com:8443/svn/RouteMatch -r 75412 Authentication realm: <https://subversion.routematch.com:8443> VisualSVN Server Password for 'SVNRead': *************** ----------------------------------------------------------------------- ATTENTION! Your password for authentication realm: <https://subversion.routematch.com:8443> VisualSVN Server can only be stored to disk unencrypted! You are advised to configure your system so that Subversion can store passwords encrypted, if possible. See the documentation for details. You can avoid future appearances of this warning by setting the value of the 'store-plaintext-passwords' option to either 'yes' or 'no' in '/home/notroot/.subversion/servers'. ----------------------------------------------------------------------- Store password unencrypted (yes/no)? no svn: E175002: Unexpected HTTP status 500 'Internal Server Error' on '/svn/RouteMatch/!svn/rvr/62094' svn: E160006: Additional errors: svn: E160006: No such revision 75412 Yet when configuring the SCM in the admini console i get this. I don't know how to troubleshoot. If it is configuration on the SVN server side, i need to know how to prove that. The Certificate is signed and installed. Error: Invalid input: Version control server configuration error: Could not create valid Subversion configuration based on configured repository url: svn: E230001: Unable to connect to a repository at URL 'https://subversion.routematch.com:8443/svn/RouteMatch' svn: E230001: Server SSL certificate verification failed: issuer is not trusted If i change the name of the server to the local name which doesn't match the certificate i get this error. Error: Invalid input: Version control server configuration error: Could not create valid Subversion configuration based on configured repository url: svn: E230001: Unable to connect to a repository at URL 'https://rmfile02.routematch.local:8443/svn/RouteMatch' svn: E230001: Server SSL certificate verification failed: certificate issued for a different hostname, issuer is not trusted2.9KViews0likes0CommentsRe: Google Chrome's connection attempt to 10.7.1.57 was rejected. The website may be down, or your network may not be properly configured.
well i jumped the gun and reinstalled. That worked but i lost my prior configuration. Not a big deal since this is only a test environment. If this happens again, know what you would want. I didn't know there was a Collaborator service. I will try that too. thx for the reply1.7KViews0likes0Comments