OCP build is an asset

All

Being able to use OCP build configuration is a strong feature that improves the speed of deployment by a long margin.

Building images via docker/podman can be an very streamlined process, but build config directly on OCP provides a fast deployment procedure straight to be able to deploy pods/containers in such a way that the changes are applied very fast.

One does not need to use Tekton/Pipelines to be able to build a complete new image with complex settings, either with git source, dockerfile, or custom strategies. The deprecation of jenkins build configurations going towards Pipeline deployment – with Operator (with tasks that compose pipeline).

A simple build can be done in OCP in a few minutes and the image build straight to ImageStream, that can be used on the spot.

I mean, it is simple, powerful, easy to debug and can deploy containers (and therefore test images) on the spot right there and then. It is also very simple to debug – MAVEN settings can be easily added on the build. I like very much that the build has the logs so well linked so then the pods show the step done.