Codeship vs Jenkins vs Travis CI

Overview

Codeship

Stacks1.0K

Followers730

Votes1.5K

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Codeship vs Jenkins vs Travis CI: What are the differences?

Introduction:

When comparing continuous integration tools like Codeship, Jenkins, and Travis CI, there are key differences that cater to specific needs of developers and organizations.

Ease of Use and Setup: Codeship provides a simple, user-friendly interface that allows for quick setup and integration with popular version control systems like GitHub and Bitbucket. Jenkins, on the other hand, requires more manual configuration and setup, making it less user-friendly for beginners. Travis CI falls in between, offering a balance of ease of use and configurability.
Scalability: Jenkins is highly customizable and scalable, making it suitable for large organizations with complex build pipelines and diverse development environments. Codeship and Travis CI are more streamlined, making them better suited for smaller teams or projects that do not require extensive customizations.
Community Support: Jenkins has a large and active community that offers a wide range of plugins, extensions, and resources for users. Codeship and Travis CI also have supportive communities, but they may not have as extensive a range of resources available as Jenkins.
Deployment Options: Codeship offers built-in deployment options for popular platforms like Heroku, AWS, and Docker, making it easy to deploy code directly from the CI/CD pipeline. Jenkins and Travis CI support custom deployment scripts but may require more manual configuration for specific deployment needs.
Pricing Model: Codeship and Travis CI offer cloud-hosted solutions with tiered pricing plans based on usage and features. Jenkins is open-source and free to use, but users are responsible for hosting and maintaining their own Jenkins servers, which can incur additional costs for infrastructure.
Extensibility and Integrations: Jenkins is known for its extensive plugin ecosystem that allows for seamless integrations with various tools and platforms. Codeship and Travis CI also offer integrations but may not have as wide a range of plugins available as Jenkins.

In Summary, when choosing between Codeship, Jenkins, and Travis CI, consider factors such as ease of use, scalability, community support, deployment options, pricing model, and extensibility to find the best fit for your development needs.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Codeship, Travis CI, Jenkins

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

Engineering Team Lead at DCMN GmbH

Oct 22, 2021

Decided

Github Actions allowed us to drop previous CI/CD technologies like Jenkins or AWS CodeBuild. The main advantages for us are:

The Infrastructure-as-Code approach of Github Actions enables us to keep CI/CD configurations next to the code.
Github as a single platform for repositories and CI/CD simplifies our stack and effort to manage it on the daily basis.

TVcloud Team <3 Github Actions

72.2k views72.2k

Comments

Pedro Gil

Head of Engineering at lengoo GmbH

May 4, 2021

Decided

We replaced Jenkins with Github Actions for all our repositories hosted on Github. GA has two significant benefits for us compared to an external build tool: it's simpler, and it sits at eye level.

Its simplicity and smooth user experience makes it easier for all developers to adopt, giving them more autonomy.

Sitting at eye level means it's completely run and configured right alongside the code, so that it's easier to observe and adjust our builds as we go.

These two benefits have made "the build" less of a system engineer responsibility and more of a developer tool, giving developers more ownership from code to release.

77.7k views77.7k

Comments

Detailed Comparison

Codeship	Travis CI	Jenkins
Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.	Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.	In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Run you automated tests \| Easily set up Codeship with Github or Bitbucket and trigger your automated tests with a simple push to your repository.; 100 builds & 5 private projects free per month.;Free for OSS.;Configure deployment pipelines \| Set up powerful deployment pipelines that let you deploy with ease and confidence multiple times a day.;Notifications \| Intelligent notifications and integrations keep your team up-to-date.;SSH debug access \| Easily ssh into a debug build to get more insights.;Use your resources to build amazing products. Codeship takes care of managing and scaling your test and delivery infrastructure.	Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.	Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
Statistics
GitHub Stars -	GitHub Stars -	GitHub Stars 24.6K
GitHub Forks -	GitHub Forks -	GitHub Forks 9.2K
Stacks 1.0K	Stacks 28.0K	Stacks 59.2K
Followers 730	Followers 6.7K	Followers 50.4K
Votes 1.5K	Votes 1.7K	Votes 2.2K
Pros & Cons
Pros 215 Simple deployments 179 Easy setup 159 Github integration 147 Continuous deployment 110 Bitbucket integration Cons 3 Ui could use some polishing 0 Difficult to answer build questions 0 Antiquated ui	Pros 506 Github integration 388 Free for open source 271 Easy to get started 191 Nice interface 162 Automatic deployment Cons 8 Can't be hosted insternally 3 Feature lacking 3 Unstable 2 Incomplete documentation for all platforms	Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Lack of support 7 Limited abilities with declarative pipelines
Integrations
Slack GitLab CI GitHub HipChat Google Compute Engine Ninefold Amazon EC2 Google App Engine AWS CodeDeploy Bitbucket	Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	No integrations available

What are some alternatives to Codeship, Travis CI, Jenkins?

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Semaphore

Semaphore is the fastest continuous integration and delivery (CI/CD) platform on the market, powering the world’s best engineering teams.

Related Comparisons

Codeship vs Jenkins vs Travis CI: What are the differences?

Introduction:

When comparing continuous integration tools like Codeship, Jenkins, and Travis CI, there are key differences that cater to specific needs of developers and organizations.

Ease of Use and Setup: Codeship provides a simple, user-friendly interface that allows for quick setup and integration with popular version control systems like GitHub and Bitbucket. Jenkins, on the other hand, requires more manual configuration and setup, making it less user-friendly for beginners. Travis CI falls in between, offering a balance of ease of use and configurability.
Scalability: Jenkins is highly customizable and scalable, making it suitable for large organizations with complex build pipelines and diverse development environments. Codeship and Travis CI are more streamlined, making them better suited for smaller teams or projects that do not require extensive customizations.
Community Support: Jenkins has a large and active community that offers a wide range of plugins, extensions, and resources for users. Codeship and Travis CI also have supportive communities, but they may not have as extensive a range of resources available as Jenkins.
Deployment Options: Codeship offers built-in deployment options for popular platforms like Heroku, AWS, and Docker, making it easy to deploy code directly from the CI/CD pipeline. Jenkins and Travis CI support custom deployment scripts but may require more manual configuration for specific deployment needs.
Pricing Model: Codeship and Travis CI offer cloud-hosted solutions with tiered pricing plans based on usage and features. Jenkins is open-source and free to use, but users are responsible for hosting and maintaining their own Jenkins servers, which can incur additional costs for infrastructure.
Extensibility and Integrations: Jenkins is known for its extensive plugin ecosystem that allows for seamless integrations with various tools and platforms. Codeship and Travis CI also offer integrations but may not have as wide a range of plugins available as Jenkins.

Codeship vs Jenkins vs Travis CI

Overview