Popular posts

I recently started integrating Drone at our organization. Here's my take away -

1. The cloning step is a bit messed up. I ended up writing a custom clone step as it is a known bug in Github that the webhook for PR creation is fired before the merge reference is created. They call it an undocumented feature primarily for their UI and not for workflows. This is my drone.yml - github.com/moengage/ci-test/blob/feature/amaze/.d…
2. The plugins are a bit confusing to set up at first, especially slack. They are poorly documented.
3. If you using for a public repository where you allow anyone to make a PR and which triggers the build, they can potentially echo all your secrets and env variables as it considers the drone.yml of the HEAD branch.

But once I got around completing the experiments and using the plugins, workflow became so much more easier. Whenever a PR is raised for qa , the QA team is notified automatically and they can proceed with the exploration tests and approve for release.

We are planning to integrate all new projects with Drone. It is much more easier to use and understand (once the initial setup is done). But we aware that it's not yet as polished as Travis or the likes. But it is definitely worth the effort!

If you are an individual developer or part of a small team (3-6 people), going for self-hosted solution will not make sense as it adds an overhead of maintenance for the service. Being part of a larger team where the ownership can be defined, shared and transferred will help you explore Drone properly.