Practical Comparison — From Jenkins to Drone CI

I am currently migrating from Jenkins to Drone CI after more than 3 years serving Jenkins as a pipeline service for a large organizations. While i am migrating, i found it’s useful to share my observations instantly. That’s why, this article will be continuously updated based on my knowledge expansion on Drone CI.

1. Pipeline Configuration as Code

  • Jenkins

it’s a file called by default “Jenkinsfile” to be added in your app git repo. It should be implemented with Groovy programming language

  • Drone CI

it’s a file called by default “.drone.yml” to be added in your app git repo. It should be implemented with YAML programming language.

2. Standarization Layer

  • Jenkins

Jenkins provides the concept of library which can be configured in 3 steps :

a. a library is a git repository (.ie. https://git.example/jenkins-lib.git )with at least a subdirectory called “vars” and one step i.e. “vars/my_step.groovy”

b. Then, you can configure your jenkins instance with this library under Configure > Global Pipelines section

Or using config-as-code

c. You use it in your Jenkinsfile as following

  • Drone CI

a. So you define a template

and this is an example of jsonnet template (

b. then you persist this template using drone CLI:

this is a live demo as well

3. In-pipeline Reusability

  • Jenkins

Just define your reusable block as a groovy function at the top or at the bottom, then call that function

  • Drone CI

Use the built-in feature of YAML of reusing blocks of yaml. Make sure that your YAML template (block) is prefixed by “x-”

4. Parallelism (Steps Execution )

  • Jenkins

Can be done thru parallel {} step.

example before parallelism

example refactor for parallelism

  • Drone CI

By default, steps run sequentially. As soon, as you start using “depends_on” key word, you break this sequence run, and parallelism can be enabled implicitly.

example before parallelism

example refactored for parallelism ( build-x and build-y to run in parallel)

5. Global secrets

  • Jenkins

You can define them in your admin dashboard Configure > Credentials

OR using config-as-code

Then, in your pipeline, you can use it as following:

  • Drone CI:

Define your secret at organization leve using drone CLI

then use it in pipeline as following:

6. External Secrets — Kubernetes Secrets

  • Jenkins

it requires to install kubernetes plugin,configure a cloud ( kubernetes cluster where agents will be provisioned) then you can define your Pod template.

In the pod template, you can attach whatever k8s secret as env variables

  • Drone CI

It requires to run Drone CI in kubernetes with pipeline of type: kubernetes

it requires to install kubernetes runner : drone-runner-kube

It requires to install the extension: drone-kubernetes-secrets

Then you can use it as following :

7. Trigger for specific files/folders updates

Jenkins: Built-in by using when { changeset "my-dir/*"} keyword

Drone CI: check extensions mentioned here


My course about cloudnative with docker and docker compose

Comparison between Jenkins and Drone CI Will be continuous updated

Stay tuned!

Software engineer, Cloud Architect, 5/5 AWS|GCP|PSM Certified, Owner of