Creating a full CI/CD pipeline

Now that you created a Jenkins instance and configured a Jenkins build in OpenShift®, you can go further on. The next steps can be creating a full CI/CD pipeline using Dependency Based Build (DBB), Artifactory and UrbanCode® Deploy (UCD) in the context of OpenShift. You can follow the tutorial Build a pipeline with Jenkins, Dependency Based Build, and UrbanCode Deploy to understand how to use these tools to create a full CI/CD pipeline for the GenApp CICS® application.

Click the following links to learn how to install these tools in OpenShift:

For DBB, see Installing and Configuring the DBB server in a Red Hat OpenShift cluster.
For UCD, see Installing the server in an OpenShift/Kubernetes cluster.
For Artifactory, you have the following two installation options:
- Deploy the Enterprise version from the OpenShift OperatorHub, as shown in the following screen capture:
- Install the Helm Chart version of Artifactory OSS, as it is explained in JFrog Artifactory OSS Helm Chart.

Creating a full CI/CD pipeline with GitLab CI

Instead of creating a Jenkins instance and configuring a Jenkins build, you can use GitLab CI. It is a service included in GitLab. When developers deliver code modifications, it triggers a pipeline that automatically builds, tests, and deploys the application into the target environment. You can follow the tutorial Build a pipeline with GitLab CI, IBM Dependency Based Build, and IBM UrbanCode Deploy to understand how to take full advantage of GitLab CI in your pipeline.

You can use all the other produts previously mentioned (DBB, UCD, and Artifactory) to build a full CI/CD pipeline.