IBM Sterling B2B Integrator - B2Bi – OCP CI/CD Pipeline

Here the ‘pull-image’ is a ‘skopeo copy’ task used to move the image from the B2Bi Entitlement Registry to the OCP internal registry. The remaining tasks are ‘trigger jenkins job’ which calls corresponding Jenkins job which performs tasks like pulling helm charts from production location to local client node, setting up the local client node, setting up pre-requisites and finally do a helm install.
Once the successful execution of this pipeline, B2Bi Sterling Integrator and SFG will be deployed on the OCP cluster environment and we can access the dashboard using the URLs under ‘Routes’

To summarize, OCP CI/CD pipeline is a steppingstone for many B2Bi customers who want to move to cloud. They can take a reference from this blog that can help them to setup pipeline in a TEST environment before moving to production. Having a CI/CD pipeline in a cloud environment will save a lot of time as it can do multiple things with just a single click – depicted in the pipeline above.

The subsequent version of this blog will have more additions to the pipeline. The plan is to extend it to a stage where post helm installs, the pipeline is capable enough to extend a B2Bi image (adapters/BP), running automation suites, security scans. Based on the results, the same image can be pushed to production environment.