Drone.io vs Github Actions

Overview

Drone.io

Stacks884

Followers456

Votes258

GitHub Actions

Stacks48.2K

Followers3.1K

Votes27

Drone.io vs Github Actions: What are the differences?

Cost: A key difference between Drone.io and GitHub Actions is the cost. Generally, Drone.io is considered to be more cost-effective as it offers unlimited build minutes for open-source projects and has a lower pricing tier for private repositories. On the other hand, GitHub Actions has a usage-based pricing model and the costs can add up depending on the number of workflows and resources used.
Native Integration: Another important difference is how Drone.io and GitHub Actions integrate with their respective platforms. Drone.io is designed to work seamlessly with various source code management systems including GitHub, GitLab, and Bitbucket. Although GitHub Actions is specifically built for GitHub projects, it has native integration and provides a more streamlined experience for GitHub repositories.
Flexibility: When it comes to flexibility, Drone.io tends to offer more options. It allows users to define their build logic through a configuration file written in YAML, giving them complete control over the build process. GitHub Actions, although it allows customization through YAML-based workflows, has some limitations in terms of what can be configured or modified.
Community and Ecosystem: GitHub Actions, being a part of the widely-used GitHub platform, benefits from a larger community and ecosystem. This means that there are more pre-built actions and integrations available, making it easier to find and use existing solutions. Drone.io, while having its own active community, might have a relatively smaller pool of available resources compared to GitHub Actions.
Self-hosted Option: One advantage of Drone.io over GitHub Actions is the ability to self-host the Drone server. Organizations that prioritize security or have specific infrastructure requirements can host their own Drone server, allowing them to have complete control over the build environment. This self-hosted option is not available with GitHub Actions.
Parallelism and Scalability: In terms of parallelism and scalability, GitHub Actions has an edge over Drone.io. GitHub Actions supports parallel and matrix builds out of the box, allowing for concurrent execution of jobs across different platforms and configurations. Drone.io, while it also supports parallel execution, might require additional configuration and setup for achieving similar scalability.

In Summary, Drone.io and GitHub Actions differ in cost, native integration, flexibility, community and ecosystem, self-hosted option, and scalability.

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 Drone.io, GitHub Actions

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

Detailed Comparison

Drone.io	GitHub Actions
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.	It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
Free for open-source;GitHub, BitBucket integration;Browser testing;Deplot with Amazon, Heroku, Google AppEngine;Flexible scripting;Team billing;	Multiple workflow files support; Free and open source; Workflow run interface; Search for actions in GitHub Marketplace; Integrated with Github's Checks API; Logs and artifacts downloading support
Statistics
Stacks 884	Stacks 48.2K
Followers 456	Followers 3.1K
Votes 258	Votes 27
Pros & Cons
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 8 Integration with GitHub 5 Free 3 Easy to duplicate a workflow 3 Ready actions in Marketplace 2 Configs stored in .github Cons 5 Lacking [skip ci] 4 Lacking allow failure 3 Lacking job specific badges 2 No ssh login to servers 1 No manual launch
Integrations
Docker Bitbucket Google App Engine Heroku GitHub Amazon S3 dotCloud	GitHub

What are some alternatives to Drone.io, GitHub Actions?

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.

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.

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.

Airflow

Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.

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.

Related Comparisons

Drone.io vs Github Actions: What are the differences?

Cost: A key difference between Drone.io and GitHub Actions is the cost. Generally, Drone.io is considered to be more cost-effective as it offers unlimited build minutes for open-source projects and has a lower pricing tier for private repositories. On the other hand, GitHub Actions has a usage-based pricing model and the costs can add up depending on the number of workflows and resources used.
Native Integration: Another important difference is how Drone.io and GitHub Actions integrate with their respective platforms. Drone.io is designed to work seamlessly with various source code management systems including GitHub, GitLab, and Bitbucket. Although GitHub Actions is specifically built for GitHub projects, it has native integration and provides a more streamlined experience for GitHub repositories.
Flexibility: When it comes to flexibility, Drone.io tends to offer more options. It allows users to define their build logic through a configuration file written in YAML, giving them complete control over the build process. GitHub Actions, although it allows customization through YAML-based workflows, has some limitations in terms of what can be configured or modified.
Community and Ecosystem: GitHub Actions, being a part of the widely-used GitHub platform, benefits from a larger community and ecosystem. This means that there are more pre-built actions and integrations available, making it easier to find and use existing solutions. Drone.io, while having its own active community, might have a relatively smaller pool of available resources compared to GitHub Actions.
Self-hosted Option: One advantage of Drone.io over GitHub Actions is the ability to self-host the Drone server. Organizations that prioritize security or have specific infrastructure requirements can host their own Drone server, allowing them to have complete control over the build environment. This self-hosted option is not available with GitHub Actions.
Parallelism and Scalability: In terms of parallelism and scalability, GitHub Actions has an edge over Drone.io. GitHub Actions supports parallel and matrix builds out of the box, allowing for concurrent execution of jobs across different platforms and configurations. Drone.io, while it also supports parallel execution, might require additional configuration and setup for achieving similar scalability.

In Summary, Drone.io and GitHub Actions differ in cost, native integration, flexibility, community and ecosystem, self-hosted option, and scalability.

Drone.io vs Github Actions

Overview