Skip to content

OpenShift Pipelines

Deploying Jenkins on OpenShift

Jenkins Container Images in OpenShift

External Jenkins Integration with OpenShift

Improving Jenkins’ performance on Openshift

Building applications in OpenShift

OpenShift Pipelines with Build Config

OpenShift Pipelines with S2i

OpenShift Pipelines with S2i and Jenkins Blue Ocean. Deploying Blue Ocean on OpenShift

OpenShift Deployments with Deployment Descriptor

OpenShift Deployments with GitHub Actions

Deployments with OpenShift HA in Multiple Datacenters

ODO - OpenShift Command line for Developers

All about OpenShift Pipelines

Jenkins CICD Getting started with Groovy and Docker Containers

Fabric8 Pipeline Library (deprecated)

Eclipse JKube Pipeline Library (formerly known as Fabric8 Kubernetes Plugin). Kubernetes & OpenShift Plugins

  • Eclipse JKube 🌟 Cloud-Native Java Applications without a hassle. Eclipse JKube is a collection of Maven and Gradle plugins, and libraries that are used for building container images using Docker, JIB or S2I build strategies. Eclipse JKube generates and deploys Kubernetes/OpenShift manifests at compile time too. It brings your Java applications on to Kubernetes and OpenShift by leveraging the tasks required to make your application cloud-native. Eclipse JKube also provides a set of tools such as watch, debug, log, etc. to improve your developer experience.
  • GitHub: Eclipse JKube

Jenkins Pipelines with OpenShift 3

OpenShift Jenkins Pipeline (DSL) Plugin. Scripted Syntax (Groovy DSL syntax) VS Declarative Syntax

  • Building Declarative Pipelines with OpenShift DSL Plugin 🌟🌟:
    • Jenkins Pipeline Syntax: Scripted Syntax (Groovy DSL syntax) & Declarative Syntax 🌟:
      • Version 2.5 of the “Pipeline plugin” released in 2016/05/16 introduces support for Declarative Pipeline syntax.
      • Declarative Pipeline is a relatively recent addition to Jenkins Pipeline which presents a more simplified and opinionated syntax on top of the Pipeline sub-systems.
    • Jenkinsfiles have only become an integral part of Jenkins since version 2 but they have quickly become the de-facto standard for building continuous delivery pipelines with Jenkins. Jenkinsfile allows defining pipelines as code using a Groovy DSL syntax and checking it into source version control which allows you to track, review, audit, and manage the lifecycle of changes to the continuous delivery pipelines the same way that you manage the source code of your application.
    • Although the Groovy DSL syntax which is referred to as the scripted syntax is the more well-known and established syntax for building Jenkins pipelines and was the default when Jenkins 2 was released, support for a newer declarative syntax is also added since Jenkins 2.5 in order to offer a simplified way for controlling all aspects of the pipeline. Although the scripted and declarative syntax provides two ways to define your pipeline, they both translate to the same execution blocks in Jenkins and achieve the same result.
    • The declarative syntax in its simplest form is composed of an agent which defines the Jenkins slave to be used for executing the pipeline and a number of stages and each stage with a number of steps to be performed.
  • Dzone - Continuous Delivery with OpenShift and Jenkins: A/B Testing 🌟
  • OpenShift 3.11 Pipeline Builds with OpenShift Jenkins Image and OpenShift DSL

Red Hat Communities of Practice

Jenkins Pipelines in OpenShift 4

OpenShift Pipelines (aka Tekton CI/CD Pipelines)

Tekton and Tekton Pipelines


Click to expand!


Click to expand!
Back to top