Assembla uses Subversion 1.12.2 and we highly recommend customers to use SVN 1.12+ based clients for the best experience. If you are using an outdated, pre-1.12 client, you should consider upgrading otherwise SVN stability will suffer significantly.
If you are having issues, here’s a quick list of the most common problems to check:
- You are using the latest possible SVN Client version;
- You have the appropriate permissions to commit/checkout your Assembla repository;
- Your Assembla space is not restricted;
- Your Internet connection is stable;
- In case of authentication issues, make sure to clear cached credentials. On UNIX-based systems, authentication data should be stored in
$HOME/.subversion/auth
. Windows systems store auth data in%APPDATA%\Subversion\auth;
. - Use version 1.12+, as there were various fixes to HTTP/HTTPS client-side implementation starting with 1.8.10;
- If all of the above is true and you are still experiencing issues, try to perform a fresh checkout into a brand new folder.
Still experiencing issues?
- Your SVN client name and version?
- Operating System name and version?
- SVN repository URL (checkout URL or SVN tool URL you see in the address bar)?
- Approximate size of your SVN repository?
- Nature of repository files – like having a large amount of small files, or large binary files inside?
- Traceroute results to subversion.assembla.com?
- Is it only one (or some) of your Assembla repos having the problem, versus all your repos?
- Are all users on experiencing the problem, or only some users?
- Are the affected users all at the same location?
- If an answer for (9) is yes, can some of them try the same operation on the same repo from a different location?
- Have you seen this problem in the past? If so, did it require a fix from us?
- At what time, UTC, did this current problem start?
- Did you try via command line?
- Is your internet speed to all other websites as fast as usual?
- Did you check with your Networking team for any issues on your company’s end?
- Additional details – e.g. are you checking out the whole repository, or a single directory like /trunk etc.;
- If you are using SVN with Jenkins – let us know the Jenkins SVN Plugin version and the Java version you have installed on a server.
Please note that most of the issues are client-specific. To make sure the issue is specific to your particular SVN client, please use the command line client instead.
Latest posts by Rajesh Kumar (see all)
- Best AI tools for Software Engineers - November 4, 2024
- Installing Jupyter: Get up and running on your computer - November 2, 2024
- An Introduction of SymOps by SymOps.com - October 30, 2024