CloudBees Continuous Integration (formerly the CloudBees Jenkins Platform) is a continuous integration (CI) and continuous delivery (CD) solution that extends Jenkins. Developed for on-premise installations, CloudBees CI offers stable releases with monthly updates, as well as additional proprietary tools and enterprise features to enhance the manageability and security of Jenkins. CloudBees CI helps administrators manage growing installations due to ever-increasing teams, projects and jobs…
N/A
Travis CI
Score 7.3 out of 10
N/A
Travis CI is an open source continuous integration platform, that enables users to run and test simultaneously on different environments, and automatically catch code failures and bugs.
$69
per month
Pricing
CloudBees Continuous Integration
Travis CI
Editions & Modules
No answers on this topic
1 Concurrent Job Plan
$69
per month
Bootstrap
$69
per month 1 concurrent job
2 Concurrent Jobs Plan
$129
per month
Startup
$129
per month 2 concurrent jobs
5 Concurrent Jobs Plan
$249
per month
Small Business
$249
per month 5 concurrent jobs
Premium
$489
per month 10 concurrent jobs
Platinum
$794+
per month starting at 15 concurrent jobs
Free Plan
Free
Offerings
Pricing Offerings
CloudBees Continuous Integration
Travis CI
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
Discount available for annual pricing.
More Pricing Information
Community Pulse
CloudBees Continuous Integration
Travis CI
Considered Both Products
CloudBees Continuous Integration
Verified User
Anonymous
Chose CloudBees Continuous Integration
Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are …
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.
Jenkins is probably the leading choice for automation and has loads of features and a large community behind it, but it can be overkill for many projects. It also has more of a web 1.0 look and interface. CircleCI is another similar big competitor, but cannot compete with Travis …
There are a few other options out there, CircleCI, Codeship and Wrecker would be a few good ones I can also recommend, each one has its particularity but I believe Travis has the best interface and flexibility of all of them. I'd recommend trying them all and seeing which one …
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 …
There are a number of alternatives to Travis CI, but Travis remains the most popular, since it was one of the first to show up. It has a lot of examples, support for building dozens of languages, and good documentation. Significant portions of the system are open source, so you …
If you're running Jenkins in your enterprise and it's in the critical path of your software pipelines, I highly recommend CloudBees Jenkins over the open source version of the product to ensure you've got the customer and technical support you'll need for your Jenkins platform to be successful.
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.
It's simple and easy to get started (it can detect the language being used based on build configuration files like a Maven pom.xml).
It's free (as in beer) for open source projects.
It has a responsive staff (you can file issues on GitHub to ask for new languages or packages to be supported, and the turnaround time isn't too bad for the free offering).
The user interface is beautiful and easy-to-use, including features like live-tailing in-progress builds.
It supports specifying private environment variables and encrypted credentials, so that you can safely automate deployments (for example, pushing built docker images to DockerHub).
Travis CI is a fairly mature platform now, and most, if not all of the common complaints have been improved. This includes documentation and logs with color support.
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.
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.
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.
Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are difficult to maintain and readable like groovy pipelines in Jenkins.
Jenkins is probably the leading choice for automation and has loads of features and a large community behind it, but it can be overkill for many projects. It also has more of a web 1.0 look and interface. CircleCI is another similar big competitor, but cannot compete with Travis CI's free account [in my opinion].