Likelihood to Recommend For all continuous integration features like multi branch pipeline, continuous build, and deployment execution, highly customizable groovy scripting, well integration with most of repositories like SVN, GIT, etc. are some of the exceptional features which helps devOps related tasks a treat to work everyday. With some minor changes in agent configuration and handling of their configuration on master instances would reduce a lot of issues. Also, cache of maven handling on agents needs to be improved (though not related to tool but the CI pipelines). But, since this is a very mature and performant tool, we expect some out of the box functionalities to handle all such scenarios. Overall, the tool works wonders because of its highly customizable features.
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 Customer Support Solutions engineering 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 File or Workspace Management Agent configurations at master level Better Support for issues in product 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 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 Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.
Read full review 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 CloudBees Jenkins Support is on par with the other enterprise tools we're currently using. It has performed well enough that we've adopted the product and placed it in the critical path of our software delivery pipelines.
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 Positive - Handles number of requests Positive - Customizations of pipelines helps integrate many type of frameworks Negative - Cache management on agents for dependencies downloaded Positive - credential management helps reduce configurations to be done for each project job at manual level 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