Apache Subversion Information Reviews & Insights

Score8 out of 10

56 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.

Reviews

3 Reviews

Information

SVN Apache-Report

Rating: 8 out of 10

Incentivized

April 8, 2021

Use Cases and Deployment Scope

Used mainly as a collective tool for version tracking to ensure revisions are tracked by the dev team, and all maintain branches of our team/project repositories. To commit the revisions once all devs have merged code from respective timelines.

Pros

Easy install
Integrates into agile project standards
Revision regressions tracking in projects

Cons

Requirements more straight forward (CVS editing options)
Some packaged dependencies are unnecessary
Potential for vendor packaged security issues

Likelihood to Recommend

Can be [suited] for teams building solutions and manage code file versioning. Subversion for us simplifies the changes per file and code version before merging to branch for continuous integration and eventually deployment. With Apache Subversion in the process of our agile development, we can continue to automate deployment as much as possible with versioning.

Rob Domenico

Senior Systems Administrator in Information Technology at Bentek Inc. (Computer Software, 51-200 employees)

Vetted Review

4 years of experience

View profile

Good and solid version control system

Rating: 7 out of 10

Incentivized

March 20, 2021

Use Cases and Deployment Scope

We used Apache Subversion to manage and control source code for our development team. Subversion helps to track, version, and manage conflicts when a file is being worked on by different team members at the same time. It allows changes to happen in parallel, keeps track of exactly what, when, and who has made the change, and allows us to revert back if necessary.

Pros

Track and control concurrent versions of the same files.
Has good support from many different software, including visualization, DevOps toolchain.
Well documented and understood by developers as it has been around for a long time.

Cons

Does not support distributed environment unlike Git.
Merging can be painful.
Does not natively support advanced features such as pull requests.

Likelihood to Recommend

Generally speaking, distributed version control systems (DVCS) such as Git have taken over the version control market (e.g. Github), but if your organization is mostly centrally located and is not already using something like Git, SVN can still get the job done and do it well.

Verified User

Employee in Information Technology (Computer Software company, 1-10 employees)

Vetted Review

8 years of experience

SVN! the best open version control ever!

Rating: 10 out of 10

Incentivized

March 24, 2017

Use Cases and Deployment Scope

I have used apache subversion for a course that I have taken and also for a company that I intern for. It is used for collaborating projects with team members. At the university level, apache subversion is a mandatory version control [solution] to be used in many courses and an option in many other courses in the fields related to computers. At an organizational level, at the company that I currently intern for, apache subversion is used by the whole software department over 3 different countries to collaborate over the huge project we are working on. Apache Subversion is a simple tool used to keep all the people working on a project on the same page by letting everybody work on the same project at the same time.

Pros

Old is gold. Apache Subversion has existed before many other version control systems, including Git. It's old, stable, and easy to use with not many complications.
Excellent versioning system. You can jump between any particular version of your project to any other version just by reverting or updating, you can also create patches of your own changes and then apply the patch on your own system on a different check out or on someone else's computer who has a checkout copy.
You can search for any older commit by using words used in the comment log or by using an exact commit number or anything in between. You can also check the log of each and every individual file instead of the whole checkout.
Tortoise SVN is a client for Apache Subversion. It has one of the best UIs I have ever seen for a version control system.

Cons

Merge conflicts is one area where I think that Apace Subversion can improve a lot in. Where there is a single file being edited by two different people and the person who tries to update after someone before him commits with changes on the same file then Subversion tries to merge the changes and create an ideal file but fails miserably.
Any file renames or deletion or additions have to be specifically made through Apache Subversion or has to be notified to Apache Subversion in a round about fashion or it will be disregarded while committing the changes. While this is reasonable, it is quite annoying until a user gets used to it.
Faster on Linux and slower on Windows. Apache Subversion can be improved by increasing its checkout, update and commit speeds on Windows.

Likelihood to Recommend

I would recommend using Apache subversion for any kind of project no matter the size or type of the project. It is very well suited in scenarios where the project is being worked upon by a team, especially a large team operating over various time zones. It provides a good means of collaboration among team members, allowing them to work peacefully and time effectively. I do not recommend using apache subversion for projects that are solely documentation based because it would be an overkill. Instead you could use Google Drive for such projects.

venkat nitin panaganti

Student in Information Technology at RIT (Computer Software, 501-1000 employees)

Vetted Review

2 years of experience

View profile

Loading Reviews List....

SVN! the best open version control ever!

Rating: 10 out of 10

Incentivized

March 24, 2017

Use Cases and Deployment Scope

Pros

Old is gold. Apache Subversion has existed before many other version control systems, including Git. It's old, stable, and easy to use with not many complications.
Excellent versioning system. You can jump between any particular version of your project to any other version just by reverting or updating, you can also create patches of your own changes and then apply the patch on your own system on a different check out or on someone else's computer who has a checkout copy.
You can search for any older commit by using words used in the comment log or by using an exact commit number or anything in between. You can also check the log of each and every individual file instead of the whole checkout.
Tortoise SVN is a client for Apache Subversion. It has one of the best UIs I have ever seen for a version control system.

Cons

Merge conflicts is one area where I think that Apace Subversion can improve a lot in. Where there is a single file being edited by two different people and the person who tries to update after someone before him commits with changes on the same file then Subversion tries to merge the changes and create an ideal file but fails miserably.
Any file renames or deletion or additions have to be specifically made through Apache Subversion or has to be notified to Apache Subversion in a round about fashion or it will be disregarded while committing the changes. While this is reasonable, it is quite annoying until a user gets used to it.
Faster on Linux and slower on Windows. Apache Subversion can be improved by increasing its checkout, update and commit speeds on Windows.

Likelihood to Recommend

venkat nitin panaganti

Student in Information Technology at RIT (Computer Software, 501-1000 employees)

Vetted Review

2 years of experience

View profile