Need advice about which tool to choose?Ask the StackShare community!
Jenkins X vs OpenShift: What are the differences?
Developers describe Jenkins X as "A CI/CD solution for cloud applications on Kubernetes". Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes. On the other hand, OpenShift is detailed as "Red Hat's free Platform as a Service (PaaS) for hosting Java, PHP, Ruby, Python, Node.js, and Perl apps". OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
Jenkins X can be classified as a tool in the "Continuous Integration" category, while OpenShift is grouped under "Platform as a Service".
Some of the features offered by Jenkins X are:
- 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
On the other hand, OpenShift provides the following key features:
- Built-in support for Node.js, Ruby, Python, PHP, Perl, and Java (the standard in today's Enterprise)
- OpenShift is extensible with a customizable cartridge functionality that allows developers to add any other language they wish. We've seen everything from Clojure to Cobol running on OpenShift.
- OpenShift supports frameworks ranging from Spring, to Rails, to Play
"Kubernetes integration" is the primary reason why developers consider Jenkins X over the competitors, whereas "Good free plan" was stated as the key factor in picking OpenShift.
Jenkins X and OpenShift are both open source tools. It seems that Jenkins X with 2.81K GitHub stars and 499 forks on GitHub has more adoption than OpenShift with 915 GitHub stars and 563 GitHub forks.
According to the StackShare community, OpenShift has a broader approval, being mentioned in 50 company stacks & 52 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
BuildkiteI 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.
jFrogI 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.
GitLab CImore 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 Jenkins X
- Kubernetes integration7
- Scripted Pipelines5
- GitOps4
Pros of Red Hat OpenShift
- Good free plan98
- Open Source62
- Easy setup46
- Nodejs support42
- Well documented41
- Custom domains32
- Mongodb support28
- Clean and simple architecture27
- PHP support25
- Customizable environments21
- Ability to run CRON jobs11
- Easier than Heroku for a WordPress blog9
- Autoscaling7
- Good balance between Heroku and AWS for flexibility7
- Easy deployment7
- PostgreSQL support6
- Free, Easy Setup, Lot of Gear or D.I.Y Gear5
- Shell access to gears4
- High Security3
- Great Support3
- Its free and offer custom domain usage2
- Logging & Metrics2
- Meteor support2
- Overly complicated and over engineered in majority of e2
- Golang support2
- Secure2
- Because it is easy to manage2
- No credit card needed1
- MultiCloud1
- Runs Anywhere - AWS, GCP, Azure1
- This is the only free one among the three as of today1
- Great free plan with excellent support1
- Autoscaling at a good price point1
- Easy setup and great customer support1
- Cloud Agnostic1
Sign up to add or upvote prosMake informed product decisions
Cons of Jenkins X
- Complexity1
Cons of Red Hat OpenShift
- Decisions are made for you, limiting your options2
- License cost2
- Behind, sometimes severely, the upstreams1
