Need advice about which tool to choose?Ask the StackShare community!

Drone.io

881
451
+ 1
258
Travis CI

27.5K
6.6K
+ 1
1.7K
Add tool

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

Introduction

Drone.io and Travis CI are both popular Continuous Integration (CI) platforms that enable developers to automatically build, test, and deploy software projects. However, there are several key differences between the two platforms.

1. Deployment Options: Drone.io provides a wider range of deployment options compared to Travis CI. While Travis CI supports deployment to various platforms, such as AWS, Heroku, and Google App Engine, Drone.io offers additional options like Kubernetes, Docker Swarm, and custom shell scripts. This flexibility allows developers to choose the most suitable deployment strategy for their applications.

2. Containerization: Unlike Travis CI, which runs builds in virtual machines, Drone.io is designed around containerization. It leverages Docker containers to isolate builds, making it easier to distribute and reproduce build environments. This container-based approach provides a consistent and reproducible build environment, resulting in more reliable and trustworthy builds.

3. Self-Hosted/On-Premise Option: While both platforms offer hosted versions, Drone.io also provides a self-hosted option for organizations that prefer to run their CI infrastructure on-premise or on a private cloud. This self-hosted option allows greater control and security of the CI environment, making it a preferred choice for companies with strict compliance or regulatory requirements.

4. Plugin and Extension Ecosystem: Travis CI has a large and mature ecosystem of plugins and extensions that developers can leverage to enhance their CI pipelines. However, Drone.io has a more extensible and flexible plugin system, with the ability to create custom plugins using any programming language. This versatility enables developers to seamlessly integrate their existing workflows and tools into the CI pipeline.

5. Configuration as Code: While both platforms allow configuring builds through YAML files, Drone.io takes configuration as code to the next level. It uses a Docker-compose-like syntax for defining build steps and can also execute arbitrary shell commands. This granular control over build configuration makes it easier to define complex build pipelines and customize the build process according to specific requirements.

6. Pricing Model: Drone.io follows a different pricing model compared to Travis CI. While Travis CI offers a free tier for open-source projects and limited builds per month, Drone.io offers unlimited builds and repositories for free. However, Drone.io charges based on the number of concurrent build agents required for larger or enterprise-scale projects, whereas Travis CI offers different plans based on the number of concurrent jobs.

In summary, Drone.io differentiates itself from Travis CI by offering a wider range of deployment options, a container-based approach, a self-hosted option, a more extensible plugin system, powerful configuration as code capabilities, and a distinctive pricing model.

Advice on Drone.io and Travis CI
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 543.6K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 853.5K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Drone.io and Travis CI
Kirill Mikhailov

Jenkins is a friend of mine. 😀

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more

When choosing a tool to help automate our CI/CD, the decision came down to GitHub Actions (GA) or TravisCI. Both are great, but the team has more experience with GA. Given GAs broad support of languages and workflows, it's hard to go wrong with this decision. We will also be using GitHub for version control and project management, so having everything in one place is convenient.

See more

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container. Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website. This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

See more

We were long time users of TravisCI, but switched to CircleCI because of the better user interface and pricing. Version 2.0 has had a couple of trips and hiccups; but overall we've been very happy with the continuous integration it provides. Continuous Integration is a must-have for building software, and CircleCI continues to surprise as they roll out ideas and features. It's leading the industry in terms of innovation and new ideas, and it's exciting to see what new things they keep rolling out.

See more

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Drone.io
Pros of Travis CI
  • 51
    Open source
  • 50
    Built on docker
  • 27
    Free for open source
  • 23
    GitHub integration
  • 18
    Easy Setup
  • 17
    Hosted internally
  • 17
    Flexible scripting
  • 10
    Bitbucket integration
  • 7
    GitLab integration
  • 7
    Works with Heroku
  • 6
    Gogs integration
  • 4
    Browser testing
  • 4
    Works with Google AppEngine
  • 4
    Active Community
  • 3
    Works with Amazon
  • 2
    Works with Cloud Foundry
  • 2
    Gitea Integration
  • 1
    Configuration as code
  • 1
    Eazy to use
  • 1
    Easy tool to automate CI pipeline. Running in an hour
  • 1
    Easy pipelines
  • 1
    Only need yml config
  • 1
    Written in Go
  • 506
    Github integration
  • 388
    Free for open source
  • 271
    Easy to get started
  • 191
    Nice interface
  • 162
    Automatic deployment
  • 72
    Tutorials for each programming language
  • 40
    Friendly folks
  • 29
    Support for multiple ruby versions
  • 28
    Osx support
  • 24
    Easy handling of secret keys
  • 6
    Fast builds
  • 4
    Support for students
  • 3
    The best tool for Open Source CI
  • 3
    Hosted
  • 3
    Build Matrices
  • 2
    Github Pull Request build
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Integrates with everything
  • 1
    Caching resolved artifacts
  • 1
    Docker support
  • 1
    Great Documentation
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Ubuntu trusty is not supported
  • 1
    Free for students
  • 1
    Configuration saved with project repository
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 0
    Perfect

Sign up to add or upvote prosMake informed product decisions

Cons of Drone.io
Cons of Travis CI
  • 3
    Very basic documentation
  • 8
    Can't be hosted insternally
  • 3
    Feature lacking
  • 3
    Unstable
  • 2
    Incomplete documentation for all platforms

Sign up to add or upvote consMake informed product decisions

What is 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.

What is Travis CI?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Drone.io and Travis CI as a desired skillset
What companies use Drone.io?
What companies use Travis CI?
See which teams inside your own company are using Drone.io or Travis CI.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Drone.io?
What tools integrate with Travis CI?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Drone.io and Travis CI?
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.
Jenkins
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.
Concourse
Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives