Drone.io vs Jenkins vs Travis CI

Overview

Travis CI

Stacks28.0K

Followers6.7K

Votes1.7K

Drone.io

Stacks884

Followers456

Votes258

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Drone.io vs Jenkins vs Travis CI: What are the differences?

Introduction: When it comes to continuous integration tools, three popular options are Drone.io, Jenkins, and Travis CI. Each of these tools has its own set of features and capabilities, making them suitable for different project requirements.

Hosting and Deployment: Drone.io is a cloud-based solution, while Jenkins and Travis CI need to be hosted on your own servers. This means that with Drone.io, you don't need to worry about server maintenance and can easily scale your CI/CD pipeline as needed.
Configuration and Automation: Jenkins relies heavily on configuration files, known as Jenkinsfiles, to set up and automate the CI/CD process. Travis CI, on the other hand, uses YAML files for configuration. In contrast, Drone.io uses a simple and intuitive YAML configuration format, making it easier to set up and manage pipelines.
Scalability and Extensibility: Jenkins is highly extensible through plugins, allowing you to customize it to fit your specific needs. While Travis CI also supports plugins, Drone.io focuses on a lightweight and extensible architecture, making it easier to scale and integrate with other tools in your workflow.
User Interface: Travis CI provides a user-friendly web interface for managing builds and configurations. Jenkins, on the other hand, has a more complex and feature-rich interface that may require some learning curve. Drone.io offers a clean and modern interface, making it easy to navigate and manage your pipelines.
Resource Management: Jenkins can be resource-intensive, requiring a significant amount of server resources to run effectively. Travis CI handles resource management for you, running your builds in isolated virtual environments. Drone.io also manages resources efficiently, allowing you to optimize costs by scaling resources based on workload.
Community Support: Jenkins has a large and active community of users and developers, providing extensive documentation and support. Travis CI also has a strong community backing, with regular updates and improvements. Drone.io, while newer, has a growing community that actively contributes to the platform's development and support.

In Summary, when choosing between Drone.io, Jenkins, and Travis CI, consider factors such as hosting preferences, configuration simplicity, scalability, user interface, resource management, and community support to find the best fit for your continuous integration and deployment 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 Travis CI, Drone.io, Jenkins

Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceon

CircleCI

Drone.io

GitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M

Comments

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

Detailed Comparison

Travis CI	Drone.io	Jenkins
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.	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.	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.
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.	Free for open-source;GitHub, BitBucket integration;Browser testing;Deplot with Amazon, Heroku, Google AppEngine;Flexible scripting;Team billing;	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 28.0K	Stacks 884	Stacks 59.2K
Followers 6.7K	Followers 456	Followers 50.4K
Votes 1.7K	Votes 258	Votes 2.2K
Pros & Cons
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 Unstable 3 Feature lacking 2 Incomplete documentation for all platforms	Pros 51 Open source 50 Built on docker 27 Free for open source 23 GitHub integration 18 Easy Setup Cons 3 Very basic documentation	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
Amazon S3 Heroku AWS CodeDeploy MySQL Red Hat OpenShift Nodejitsu npm GitHub Engine Yard Cloud cloudControl	Docker Bitbucket Google App Engine Heroku GitHub Amazon S3 dotCloud	No integrations available

What are some alternatives to Travis CI, Drone.io, Jenkins?

Codeship

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.

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.

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

Drone.io vs Jenkins vs Travis CI: What are the differences?

Hosting and Deployment: Drone.io is a cloud-based solution, while Jenkins and Travis CI need to be hosted on your own servers. This means that with Drone.io, you don't need to worry about server maintenance and can easily scale your CI/CD pipeline as needed.
Configuration and Automation: Jenkins relies heavily on configuration files, known as Jenkinsfiles, to set up and automate the CI/CD process. Travis CI, on the other hand, uses YAML files for configuration. In contrast, Drone.io uses a simple and intuitive YAML configuration format, making it easier to set up and manage pipelines.
Scalability and Extensibility: Jenkins is highly extensible through plugins, allowing you to customize it to fit your specific needs. While Travis CI also supports plugins, Drone.io focuses on a lightweight and extensible architecture, making it easier to scale and integrate with other tools in your workflow.
User Interface: Travis CI provides a user-friendly web interface for managing builds and configurations. Jenkins, on the other hand, has a more complex and feature-rich interface that may require some learning curve. Drone.io offers a clean and modern interface, making it easy to navigate and manage your pipelines.
Resource Management: Jenkins can be resource-intensive, requiring a significant amount of server resources to run effectively. Travis CI handles resource management for you, running your builds in isolated virtual environments. Drone.io also manages resources efficiently, allowing you to optimize costs by scaling resources based on workload.
Community Support: Jenkins has a large and active community of users and developers, providing extensive documentation and support. Travis CI also has a strong community backing, with regular updates and improvements. Drone.io, while newer, has a growing community that actively contributes to the platform's development and support.

Drone.io vs Jenkins vs Travis CI

Overview