Apache Subversion Reviews & Insights

Score9.7 out of 10

58 Reviews and Ratings

Community insights

TrustRadius Insights for Apache Subversion are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Stability: Many users have praised Apache Subversion for its stability, with some mentioning that they have experienced almost zero downtime over several years of usage. This reliability has made it a preferred choice compared to newer version control systems.

End-to-End Visibility: Reviewers appreciate the end-to-end visibility of all changes in the project provided by Subversion. This feature allows for effective revision control and makes it easier to track down and resolve conflicts.

Integration and Extensibility: Several users have mentioned that Subversion's integration with tools like Redmine and its ability to be extended using scripting languages like Perl are valuable features. These integrations enhance productivity and simplify workflow management.

Apache Subversion Reviews

2 Reviews

Engineering

Enjoying Apache Subversion

Rating: 9 out of 10

Incentivized

November 30, 2018

Use Cases and Deployment Scope

Subversion is being used by our engineering team to manage the development code we write for the company.

Pros

Can be used from many locations, like a cloud-based system but with more custom control--and its free!
Multiple projects easily stored in a single repository, which aids in maintenance of common code, yet also easily allows for separate repositories where no sharing is desired.
Very stable, with lots of additional tools to help maintain and examine repositories (e.g. websvn).
Much easier to understand when coming from more traditional SCM systems like CVS and Perforce (as opposed to Git, which is a bit of a paradigm shift).

Cons

Refactoring the layout of a respoitory--or a part of a repository--can be a bit painful, especially for users with workspaces associated with the affected part of the repository. Not sure what could be done to make that better, but it would be nice if something was possible.
Folks coming from Git can have problems using Subversion. Again, not sure anything can (or should) be done to address that, but it is occasionally an issue.

Likelihood to Recommend

Where multiple developers have well-defined areas of responsibility it works great! When many developers are all working in the same area of code, so changes overlap, then it is more of a challenge. But, like Git, it has pretty good merge tools to help resolve conflicts.

Alternatives

Perforce

I find Perforce to be a little more cumbersome to use than Subversion. And it is NOT free or open source.

Verified User

Engineer in Engineering (E-Learning company, 51-200 employees)

Vetted Review

18 years of experience

Git >>>>>>> Subversion

Rating: 7 out of 10

January 19, 2015

Use Cases and Deployment Scope

Subversion used to be our main version control software before we started using GitHub. But after introduction of Git, we stopped using subversion drastically . We only have a few old code projects which are still on subversion. We have decided to go ahead with Git for all new projects.

Pros

User friendly and easy to learn and understand
Free software
Easy to keep track of code versions

Cons

Not distributed like Git
Git more user friendly and advanced. Git has lot more features .

Likelihood to Recommend

If the code versioning is only needed between a few developers (with not much collaboration) and company cannot afford to buy GitHub License.

Alternatives Evaluated

Git is better than Subversion in every aspect except that is not free . But since our company has bought Git licenses and I would not go back to using Subversion .

Verified User

Engineer in Engineering (Information Technology and Services company, 10,001+ employees)

Vetted Review

5 years of experience

Loading Reviews List....