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 TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.
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 It is very simple to configure a range of environment versions and settings in a simple YAML file. It integrates very well with Github, Bitbucket, or a private Git repo. The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface. 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 I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source. There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration. 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 Usability TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.
Read full review Support Rating After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.
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
Git is the future.
Read full review Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per
TeamCity , I would never go back to using it. It's also complicated to configure but it is not worth the trouble.
Codeship supports integration with
GitHub , GitLab and BitBucket. I've only used it briefly, but it seems to be a nice tool.
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's improved my ability to deliver working code, increasing my development velocity. It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage. It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build). It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high). The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch". Read full review ScreenShots