Drone.io Reviews

I like how easy it is to set up a new CI/CD process with Drone, and also how fast multiple teams are able to make their deploys simultaneously. We used Jenkins before and it was extremely slow compared to the deployment pace Done has given us. I also love the UI and the multiple configuration options Drone provides. Documentation is good as well.

I'm not sure what to say here. I don't see anything I think I dislike at the moment.

Drone is one of the best platforms for fast and easy CI/CD at the moment.

Making CD/CD processes fast, and with little bottlenecks. Drone is also easy to configure even for engineers with not much experience with DevOps work.

The ease of use of Drone is brilliant. The setup is seamless, and the test running is brilliant.

Sometimes, it can be difficult to get repos setup with drone (with the secrets, encryption etc). But it's worth it in the end.

Running Drone in a container on a beefy host and reverse proxying works great. If you want to add some distributed computing power, you can easily add Docker hosts form other machines as nodes.

Our CI was slow and broke a lot. We wanted customization without paying a premium. Drone's plugins and open API gave us everything we could of dreamed of.

My favorite of any tool is being Open Source and distributed under a permissive license like Apache License. More specifically, it is easily up and running locally thanks to the use of Docker. Furthermore, thanks to a deep integration of Docker, containers are used to to build code and test it. As well as making the transfer form development phase to staging to production a very simple task for any developer.

A hosted alternative is also provided and it's integrated with many code hosting solutions like Github, Bitbucket.

Drone has a basic and simple UI compared to other hosted alternatives. The UI tends to make users adapt their CI process to Drone features/limitations. I was also maybe noticing that drone.io isn’t going anywhere these days. It's integration with AWS services (e.g. S3) is not perfect and has a lot of limitations.

Drone is good CI solution especially if you're looking for an on-premise solution and it's deep integration with Docker make it even better for fast builds. However, some features of Drone seem to be in beta for some time now (like S3). This gives you a strange feeling as Drone not going anywhere while most of hosted services tend to surprise their users with new features/improvement from time to time.

We use Drone.io (among other hosted solutions) to deploy specific branches of our the codebase of a front-end application to S3 and to automate some NGINX config.

Having builds in a docker container ensures that they are fast and accurate every time, builds can never interfere with each other. Any developer with commit access can be trusted to edit the build.

The UI is still maturing, the upgrade from 0.3.0 to 0.4.0 is painful but wont be a problem for new users.

Build automation, CI. Works perfectly!

Easy setup - done in several commands (get docker container and run in) - save many hours comparing to setup jvm+jenkins for example; It's fast enough to work on small ARM board - very important while deploying on ARM-farm

Little bit more complicated setup of deployment (I need deploy to many server at once and it's no option to fallback if some server fail... or I just can't find it)

Very limited resources consummation is big advantage of drone.io

Drone allowed us to instantly start CI/CD quickly and efficiently. With other tools like Jenkins you have to go through so much configuration. Drone instantly connects with most enterprise level source control systems.

Drone also leverages docker, so that any tests which can be run in a docker container can also run in Drone. This opens up a door of huge possibilities across any language, tool. If you can find it at hub.docker.com then you apply it to Drone. If some container for a specific tool, language, or combo is missing, you can always create your own and upload it to hub.docker.com and use it in Drone.

Overall the tool is great at what it does, its hard to find fault with it. But, I would say there is room for the administration capabilities of the tool. Usage reports and such.

Leverage the Open Source community around Drone. That is what has really set Drone apart in my opinion from other CI/CD solutions.

By testing our code in docker containers, we have become a more linux container centric as a team. It helped introduce docker into our workflow in a positive way, rather than a jarring new devops experience/capability. For any large enterprise looking to introduce and leverage docker as a new technology in their stack, Drone will greatly help the transition to the world of linux containers in production.

Easy to use, and so very powerful! This is the best replacement for Jenkins!

Docs can be hard to follow sometimes, but the community is amazing!

Drone.io should be your go to always!

Keeping the cogs spinning! Drone.io allows me to ensure the highest quality product before I roll out product the sales teams.

It's open source

Self hosting it is a bliss - just launch a couple docker containers

Cannot use self-hosted drone on public facing repos - too much access is being given. But I think it's solved in 0.4

Join gitter.im chat on github.com/drone/drone - the project is actively maintained and the chat has a very lively discussion

Using drone I was able to reduce my team's build times from 30 minutes to 1 minute

Brilliant "one size doesn't fit all" approach allows users to develop the plugins they need. Source control driven configuration. Platform agnostic.

The development of the open source tool is active and responsive to user feedback, as well as providing excellent support. There's an ever expanding range of plugins, both through the curated marketplace as well as others writing unofficial ones.

The documentation whilst not the most comprehensive covers most basic use cases, whilst the user community are always willing to help and the code base is fairly self documenting to understand how the internals work if needed.

The developers are also friendly and welcoming to new contributors wishing to help advance the project.

Not the easiest to scale with high availability. The single DB used for storing data on build logs etc. could be a single point of failure unless accounted for. Documentation is not always the clearest on all possible parameters etc.

Brilliantly customisable to almost any conceivable use case as long as you have a development team capable of writing self contained docker apps.

Configuration through source control avoids "special snowflake" syndrome that sometimes comes with tools like Teamcity and Jenkins.

Leverage the power of Docker quickly and easily..

A simple to use CI and CD solution, with configuration stored in source control.

Allows for focusing on development rather than CI and CD whilst integrating beautifully with a range of source control providers.

Drone.io was a clear standout in Continuous Integration daemon category.

It's looks & configuration are simplistic yet very powerful which is a considerable breath of fresh air in a marketplace full of ugly & difficult to use CI products (Cruisecontrol, Jenkins and GoCD to name a few)

- excellent documentation

- lots of plugins

- plenty of active development & investment by the community

- great github integration

- simplistic & no fuss UI

- matrix based builds

Drone.io is big into docker, and sadly this is where I feel it's considerably let down by a technology which is still very much evolving & not really ready for prime time.

- struggled heavily to have Drone.io work in a stable & reproducible fashion with docker-swarm, even though I had it up & running in a day & it wasn't Drone.io's fault

- no parallel jobs (yet) making it hard to scale out a build with a lot of unit tests

- docker ...

- no current integration with Amazon ECS (though I imagine that there'll be a plugin for it soon)

- docker-in-docker is a complete nightmare if you want to create docker images to publish

- no ability to use a slave other than docker (at this point)

Eventually I had to abandon using Drone.io & was forced to pick Jenkins as a replacement namely because trying to get docker production ready was more trouble than it was worth

Do it & if you can't then watch it closely because it's making waves in a market full of really old software & ideas

Reduction in build / test time to improve product deployment throughput