Need advice about which tool to choose?Ask the StackShare community!
Blue Ocean vs Jenkins X: What are the differences?
Developers describe Blue Ocean as "A reboot of the Jenkins CI/CD User Experience". Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team. On the other hand, Jenkins X is detailed as "A CI/CD solution for cloud applications on Kubernetes". Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes.
Blue Ocean and Jenkins X belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Blue Ocean are:
- Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
- Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
- Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.
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
"Beautiful interface" is the top reason why over 4 developers like Blue Ocean, while over 2 developers mention "Kubernetes integration" as the leading cause for choosing Jenkins X.
Blue Ocean and Jenkins X are both open source tools. Jenkins X with 2.8K GitHub stars and 498 forks on GitHub appears to be more popular than Blue Ocean with 2.49K GitHub stars and 435 GitHub forks.
CityLiv, Nexus National Security Network, and iCodeBetter are some of the popular companies that use Blue Ocean, whereas Jenkins X is used by letgo, Zetaops, and Proente. Blue Ocean has a broader approval, being mentioned in 4 company stacks & 10 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 Blue Ocean
- Beautiful interface7
Pros of Jenkins X
- Kubernetes integration7
- Scripted Pipelines5
Sign up to add or upvote prosMake informed product decisions
Cons of Blue Ocean
Cons of Jenkins X