CloudBees Codeship vs. Travis CI

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CloudBees Codeship
Score 9.0 out of 10
N/A
Codeship from CloudBees is a build automation platform from the Austrian company of the same name.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 1 concurrent job
Pricing
CloudBees CodeshipTravis 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 CodeshipTravis CI
Free Trial
YesYes
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details—Discount available for annual pricing.
More Pricing Information
Community Pulse
CloudBees CodeshipTravis CI
Considered Both Products
CloudBees Codeship
Chose CloudBees Codeship
Codeship has been easier for our devops team to work with as far as making delivery plans and build scripts. Anecdotally, it has been more stable over time, cutting down on time investigating why some random part of the delivery process has broken. I am not sure why this is, …
Chose CloudBees Codeship
Back in those days, we didn't know about Gitlab, and Bitbucket didn't provide a CI pipeline. Jenkins is just too much for the simple tasks we wanted to achieve, besides, we didn't have a dedicated server for the sole purpose of having our code pipelined though continuous …
Travis CI
Chose Travis CI
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 …
Chose Travis CI
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 …
Top Pros
Top Cons
Best Alternatives
CloudBees CodeshipTravis CI
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CloudBees CodeshipTravis CI
Likelihood to Recommend
9.0
(6 ratings)
6.0
(8 ratings)
Usability
-
(0 ratings)
5.0
(1 ratings)
Support Rating
-
(0 ratings)
4.0
(1 ratings)
User Testimonials
CloudBees CodeshipTravis CI
Likelihood to Recommend
CloudBees
Codeship is extremely well suited for projects that are version controlled on public hosting such as Github or Bitbucket, and for situations where you need to pick up code from these systems and deploy it to different cloud environments. For example, we had two projects for the same client that were hosted on Github and needed to be deployed to AWS and Heroku. The native CI/CD tools of these cloud environments could not provide a holistic solution to deploy to both environments the way Codeship did.
Read full review
Travis CI
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
CloudBees
  • Codeship provides a set of tools for quickly creating and building our deployment artifacts and push them to the designated servers.
  • Codeship's hooks allows our developers to simply push tags from our git repositories to initiate a deployment of code to a server. No one outside of the devops team needs any expertise to get our code packages delivered.
  • Codeship allows us to tie in behat and unit tests easily to prevent delivery of buggy code.
Read full review
Travis CI
  • 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
CloudBees
  • I would like to see a little bit more than the green/red status. If there are tests, it would be good to see how many have failed on a red build.
  • To improve build times (and reduce feedback times), it would be good to see how long build, tests, and deployment take over time. An overview like that could very easily point to potential areas of improvement. I think Codeship users do not want to bother with the build process, but, if there is anything to improve and increase productivity it's very unlikely that users wouldn't want to do this.
Read full review
Travis CI
  • 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
CloudBees
No answers on this topic
Travis CI
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
CloudBees
No answers on this topic
Travis CI
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
Our company uses Jenkins for all internal deployment processes for one very important reason - it's hosted internally. But Codeship is great for personal use - it has intuitive UI, easy setup and tons of integrations.
Read full review
Travis CI
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
CloudBees
  • Having the code tested thoroughly. While it's obviously a part of the job that still requires the developer to sit down and to actually have some decent and thorough tests implemented, by using codeship we were able to guarantee 100% that our code was being tested each and every time it got commited and pushed onto our repositories. Leading to a faster, shorter and sure implementation iterative cycle.
  • Fewer 'man in the middle' processes which required more steps and people involved just to get the code shipped onto our deployment servers.
  • Almost inexistent learning curve. Codeship is simple to use and very intuitive. Nobody in our development department had a hard time figuring out how to have it properly configured for each new project created there.
Read full review
Travis CI
  • 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

CloudBees Codeship Screenshots

Screenshot of Get an overview of all your builds, identify failed builds easily and take action right from the dashboard.Screenshot of Information for a single build, inspect log files for each step and notice at a glance which pipeline and step are failing.Screenshot of Simply enter your setup and test commands, or choose from templates available for a wide range of stacks.Screenshot of Deploy to various web services without having to worry about the process. Simply choose your deployment target, which branch you want to deploy and off you go.Screenshot of We take care of all the complicated parts of the deployment. You simply fill in the blanks and you're all set.Screenshot of Get notifications for your builds on a multitude of services. You can also ping your own services to implement custom logic.