Likelihood to Recommend
It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
Read full review
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Read full review Pros Revision control done properly - you have end to end visibility of all changes in the project. Conflict resolution - visually highlighting the differences helps to track down the problem. Being open source and very popular. We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years. Rollbacks are made simple and easy to use. Read full review Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project. Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts. Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing. Read full review Cons Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists. Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!) Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion. Read full review Can add more build templates for specific technology requirements Can have more features in dashboards which can help dev teams stream line their tasks and priorities Can have raise alarm feature in case of any sort of failure in devops pipeline execution Read full review Likelihood to Renew
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
Read full review
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Read full review Usability
Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
Read full review Support Rating
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
Read full review Implementation Rating
Do research beforehand and, if possible, do a trial run before implementing into production environment.
Read full review Alternatives Considered Git
has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but
is the future.
Read full review
In my opinion, DevOps covers the development process end to end way better than
. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
Read full review Return on Investment Subversion helps us feel secure in maintaining access to all of our product code, both current and historical. Being free and open source makes it an even better "investment". Read full review It has streamlined the pipeline and project management for our agile effort. It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise. The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization. Read full review ScreenShots