Skip to main content
Redhat Developers  Logo
  • Products

    Platforms

    • Red Hat Enterprise Linux
      Red Hat Enterprise Linux Icon
    • Red Hat AI
      Red Hat AI
    • Red Hat OpenShift
      Openshift icon
    • Red Hat Ansible Automation Platform
      Ansible icon
    • View All Red Hat Products

    Featured

    • Red Hat build of OpenJDK
    • Red Hat Developer Hub
    • Red Hat JBoss Enterprise Application Platform
    • Red Hat OpenShift Dev Spaces
    • Red Hat OpenShift Local
    • Red Hat Developer Sandbox

      Try Red Hat products and technologies without setup or configuration fees for 30 days with this shared Openshift and Kubernetes cluster.
    • Try at no cost
  • Technologies

    Featured

    • AI/ML
      AI/ML Icon
    • Linux
      Linux Icon
    • Kubernetes
      Cloud icon
    • Automation
      Automation Icon showing arrows moving in a circle around a gear
    • View All Technologies
    • Programming Languages & Frameworks

      • Java
      • Python
      • JavaScript
    • System Design & Architecture

      • Red Hat architecture and design patterns
      • Microservices
      • Event-Driven Architecture
      • Databases
    • Developer Productivity

      • Developer productivity
      • Developer Tools
      • GitOps
    • Automated Data Processing

      • AI/ML
      • Data Science
      • Apache Kafka on Kubernetes
    • Platform Engineering

      • DevOps
      • DevSecOps
      • Ansible automation for applications and services
    • Secure Development & Architectures

      • Security
      • Secure coding
  • Learn

    Featured

    • Kubernetes & Cloud Native
      Openshift icon
    • Linux
      Rhel icon
    • Automation
      Ansible cloud icon
    • AI/ML
      AI/ML Icon
    • View All Learning Resources

    E-Books

    • GitOps Cookbook
    • Podman in Action
    • Kubernetes Operators
    • The Path to GitOps
    • View All E-books

    Cheat Sheets

    • Linux Commands
    • Bash Commands
    • Git
    • systemd Commands
    • View All Cheat Sheets

    Documentation

    • Product Documentation
    • API Catalog
    • Legacy Documentation
  • Developer Sandbox

    Developer Sandbox

    • Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new, no-cost sandbox environments.
    • Explore Developer Sandbox

    Featured Developer Sandbox activities

    • Get started with your Developer Sandbox
    • OpenShift virtualization and application modernization using the Developer Sandbox
    • Explore all Developer Sandbox activities

    Ready to start developing apps?

    • Try at no cost
  • Blog
  • Events
  • Videos

Is Jenkins showing its age for modern CI/CD? What's next?

April 20, 2016
Jason Marley
Related topics:
CI/CDDevOps
Related products:
Red Hat OpenShift

Share:

    Jenkins is great, and it has done a lot to make our lives easier. It seems like not so long ago when the idea of continuous integration tools was a daunting task. Jenkins came to the rescue, and I (and many others) use it a lot... A LOT.

    Given that my day to day work is in consulting, I'm constantly working in different development environments with different technologies - and a common thread among all those environments is Jenkins. It is pervasive, there are tons of plugins, and it is fairly easy to extend. But there are issues we used to take for granted that start to seem more problematic in today's modern ecosystem of build tools.

    The problems start arising when you're trying to build pipelines with Jenkins. Pipelines that need to build, push, and pull many different things from many different places. Each of those things generally requires some kind of plug-in, and from my experience it never quite meets 100% of my use case; something always seems to be missing

    Wouldn't it be nice to simply have a more CLI driven, programmatic approach and not have to forego power and customization for ease of use? Do we really need a GUI to help us build our builds and processes? I argue that the answer is "no".

    Here's the thing: As a developer or team lead, it is not uncommon to have to build all these processes by hand first to see how they work for your project, at which point you'll then have to re-implement it on Jenkins. So why not just reuse that initial prototype? Okay you get the point; you feel or have felt my pains, but what's next? There is a new wave of CI tools that put the power back into the developers hands.

    Tools like Travis-CI are changing the way we build CI pipelines. Since Travis integrates with GitHub, you simply add a .yaml file to your project and Travis picks this up, kicks off your first build, and you're on your way to fully automated CI.

    I also really like, and am a proponent for GitLab-CI. It is a similar concept to Travis-CI, except instead of being a Github add-on, it is all in one SCM solution and CI tool. You can set up a docker registry, and can use any of those docker containers in your CI build... Sweet! Now we can dynamically spin up an environment, test our stuff, and tear it down - no longer do we need a dedicated server for our builds. The OPS team can control which containers are available so that the environment is representative of production or staging environments, or you can "go rogue" and build the custom environment to meet your needs.

    Another cool feature of Travis CI and GitLab is the fact that the your projects CI/CD configuration is all under source control along-side the project source code, which would take an extra step be if you were using the Jenkins GUI tooling. It is true that you can write your Jenkins jobs via a DSL (and subsequently check that into version control), but doing so is extra manual work, and the scripts are written in Groovy, which I consider to be a negative.

    Funny story: Before I could finish writing this article, the Jenkins project announced Jenkins 2.0. So, it seems the Jenkins team is feeling the wind of change as well.

    I haven't had a chance to use it, but from reading the documentation it might be a good balance between ease of use (GUI), and a more common DSL. So if you're a heavy Jenkins shop, be patient. Change is coming and looks to be for the better. Happy coding!


    Editor's note: Red Hat is also focusing heavily on DevOps. More information can be found on the Red Hat Developers DevOps topic page.

    Last updated: September 7, 2023

    Recent Posts

    • Kafka Monthly Digest: September 2025

    • A more secure way to handle secrets in OpenShift

    • How to deploy MCP servers on OpenShift using ToolHive

    • How to change the meaning of python and python3 on RHEL

    • vLLM or llama.cpp: Choosing the right LLM inference engine for your use case

    Red Hat Developers logo LinkedIn YouTube Twitter Facebook

    Platforms

    • Red Hat AI
    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products

    Build

    • Developer Sandbox
    • Developer Tools
    • Interactive Tutorials
    • API Catalog

    Quicklinks

    • Learning Resources
    • E-books
    • Cheat Sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site Status Dashboard
    • Report a security problem

    RED HAT DEVELOPER

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2025 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility

    Report a website issue