Need advice about which tool to choose?Ask the StackShare community!
Drone.io vs Jenkins X: What are the differences?
What is Drone.io? Open source continuous integration platform built on Docker. 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 Jenkins X? A CI/CD solution for cloud applications on Kubernetes. Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes.
Drone.io and Jenkins X can be categorized as "Continuous Integration" tools.
Some of the features offered by Drone.io are:
- Free for open-source
- GitHub, BitBucket integration
- Browser testing
On the other hand, Jenkins X provides the following key features:
- Automated CI and CD - Rather than having to have deep knowledge of the internals of Jenkins Pipeline, Jenkins X will default awesome pipelines for your projects that implements fully CI and CD
- Environment Promotion via GitOps - Each team gets a set of Environments. Jenkins X then automates the management of the Environments and the Promotion of new versions of Applications between Environments via GitOps
- Pull Request Preview Environments - Jenkins X automatically spins up Preview Environments for your Pull Requests so you can get fast feedback before changes are merged to master
"Open source" is the primary reason why developers consider Drone.io over the competitors, whereas "Kubernetes integration" was stated as the key factor in picking Jenkins X.
Jenkins X is an open source tool with 2.8K GitHub stars and 498 GitHub forks. Here's a link to Jenkins X's open source repository on GitHub.
According to the StackShare community, Drone.io has a broader approval, being mentioned in 47 company stacks & 20 developers stacks; compared to Jenkins X, which is listed in 3 company stacks and 7 developer stacks.
We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.
Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.
We primarily need:
- Fast SBT builds (caching)
- Low maintenance overhead (ideally serverless)
- Everything as code
- Ease of use
I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:
Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.
It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.
And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 😞) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.
I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.
more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation
Weakness: * Need use gitlab as repository to bring more powerful configuration
Pros of Drone.io
- Open source51
- Built on docker50
- Free for open source27
- GitHub integration23
- Easy Setup18
- Hosted internally17
- Flexible scripting17
- Bitbucket integration10
- GitLab integration7
- Works with Heroku7
- Gogs integration6
- Browser testing4
- Works with Google AppEngine4
- Active Community4
- Works with Amazon3
- Works with Cloud Foundry2
- Gitea Integration2
- Configuration as code1
- Eazy to use1
- Easy tool to automate CI pipeline. Running in an hour1
- Easy pipelines1
- Only need yml config1
- Written in Go1
Pros of Jenkins X
- Kubernetes integration7
- Scripted Pipelines5
- GitOps4
Sign up to add or upvote prosMake informed product decisions
Cons of Drone.io
- Very basic documentation3
Cons of Jenkins X
- Complexity1
