Need advice about which tool to choose?Ask the StackShare community!

Jenkins X

149
369
+ 1
16
Red Hat OpenShift

1.5K
1.4K
+ 1
517
Add tool

Jenkins X vs OpenShift: What are the differences?

Introduction: In the world of software development, there are various tools and platforms available to streamline the process of Continuous Integration and Continuous Deployment (CI/CD). Two popular options in this space are Jenkins X and OpenShift. While both serve the same purpose, there are key differences between them. Let's explore these differences in detail.

  1. Architecture and Deployment Model: Jenkins X follows a cloud-native architecture and is primarily built for Kubernetes-based infrastructure. It integrates with various cloud providers and utilizes containerization technologies, such as Docker and Kubernetes. On the other hand, OpenShift is a comprehensive enterprise-grade container application platform that provides built-in CI/CD capabilities. It uses a combination of Docker containers, Kubernetes, and Red Hat Enterprise Linux to deliver a platform that supports the entire application lifecycle.

  2. Ease of Use: Jenkins X promotes a GitOps workflow, where the entire CI/CD pipeline is defined and version-controlled in the Git repository. The platform strives to simplify the process of setting up and managing CI/CD pipelines by providing automated project scaffolding, pipeline configuration, and environment provisioning. OpenShift offers ease of use through its web-based interface, allowing developers to easily create and manage applications without getting involved in low-level infrastructure operations.

  3. Native Kubernetes Integration: Jenkins X is specifically designed for Kubernetes and leverages its powerful native features. It automatically provisions and manages ephemeral environments for each pull request and provides preview environments for testing changes before merging. OpenShift also integrates with Kubernetes and provides additional enterprise-focused features on top of it, such as built-in monitoring, logging, and security capabilities.

  4. Community Support and Ecosystem: Jenkins X has a vibrant and active community with continuous contributions to its open-source codebase. It benefits from the wide adoption of Jenkins and Kubernetes, which translates into excellent community support and extensive integration options with other tools and services. OpenShift, being an enterprise-grade platform developed by Red Hat, has a strong backing and a dedicated support network. It offers a comprehensive ecosystem with a wide range of integrated tools and services to streamline the development and deployment process.

  5. Extensibility and Customization: Jenkins X provides an extensible plugin architecture that allows developers to customize and extend its capabilities. It supports a wide range of plugins and integrations with different tools, enabling developers to tailor the CI/CD workflow according to their project requirements. OpenShift also offers extensibility through its rich set of APIs, allowing developers to integrate with custom tools and configure advanced deployment strategies.

  6. Pricing and Licensing: Jenkins X is an open-source project under the Apache License 2.0, which means it is free to use and modify. However, depending on the cloud provider and additional services used, there may be costs associated with infrastructure resources. OpenShift, being a commercial product offered by Red Hat, has licensing costs associated with it. The pricing model varies based on the edition and support package chosen, making it suitable for enterprises looking for comprehensive support and assurance.

In summary, Jenkins X is a cloud-native CI/CD platform specifically designed for Kubernetes-based infrastructure, offering extensibility and strong community support. OpenShift, on the other hand, is an enterprise-grade container application platform that provides built-in CI/CD capabilities and a comprehensive ecosystem. The choice between them depends on factors such as the infrastructure used, the level of enterprise features required, support needs, and licensing considerations.

Advice on Jenkins X and Red Hat OpenShift
Needs advice
on
CircleCICircleCIGitLab CIGitLab CI
and
Jenkins XJenkins X

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
See more
Replies (3)
Glenn Gillen
Recommends
on
BuildkiteBuildkite

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.

See more
Recommends
on
jFrogjFrog

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.

See more
Estu Fardani
Recommends
on
GitLab CIGitLab CI

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

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Jenkins X
Pros of Red Hat OpenShift
  • 7
    Kubernetes integration
  • 5
    Scripted Pipelines
  • 4
    GitOps
  • 99
    Good free plan
  • 63
    Open Source
  • 47
    Easy setup
  • 43
    Nodejs support
  • 42
    Well documented
  • 32
    Custom domains
  • 28
    Mongodb support
  • 27
    Clean and simple architecture
  • 25
    PHP support
  • 21
    Customizable environments
  • 11
    Ability to run CRON jobs
  • 9
    Easier than Heroku for a WordPress blog
  • 8
    Easy deployment
  • 7
    PostgreSQL support
  • 7
    Autoscaling
  • 7
    Good balance between Heroku and AWS for flexibility
  • 5
    Free, Easy Setup, Lot of Gear or D.I.Y Gear
  • 4
    Shell access to gears
  • 3
    Great Support
  • 3
    High Security
  • 3
    Logging & Metrics
  • 2
    Cloud Agnostic
  • 2
    Runs Anywhere - AWS, GCP, Azure
  • 2
    No credit card needed
  • 2
    Because it is easy to manage
  • 2
    Secure
  • 2
    Meteor support
  • 2
    Overly complicated and over engineered in majority of e
  • 2
    Golang support
  • 2
    Its free and offer custom domain usage
  • 1
    Autoscaling at a good price point
  • 1
    Easy setup and great customer support
  • 1
    MultiCloud
  • 1
    Great free plan with excellent support
  • 1
    This is the only free one among the three as of today

Sign up to add or upvote prosMake informed product decisions

Cons of Jenkins X
Cons of Red Hat OpenShift
  • 1
    Complexity
  • 2
    Decisions are made for you, limiting your options
  • 2
    License cost
  • 1
    Behind, sometimes severely, the upstreams

Sign up to add or upvote consMake informed product decisions

What companies use Jenkins X?
What companies use Red Hat OpenShift?
See which teams inside your own company are using Jenkins X or Red Hat OpenShift.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Jenkins X?
What tools integrate with Red Hat OpenShift?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Jenkins X and Red Hat OpenShift?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Spinnaker
Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
Blue Ocean
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.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives