Currently we have 2 main pipelines in AMQ Streams productisation process;

1. One which builds the PNC Java artefacts and creates the CR and pushes it to staging area
2. The second one takes the output of the first (the binaries as part of the dist) and uses those to build the container images

Currently, with this setup, we struggle with creating a new CR that just includes a container image change (e.g. using a new base image for the containers). We would have to run the first pipeline to have the new CR created. But with doing this, PNC could decide to re-build Kafka for example. The knock on implications are that a whole full round of test would be needed. We need a pipeline setup to allow us;

• build or ignore the PNC Java artifact aspects, whichever is needed
• give us the capability to create a new CR and stage it (and pull in the latest available binaries)
• build the container images solely and include them in a CR

How this is achieved is to be discussed. Whether its 3 separate pipelines that can run independently or one large pipeline where certain stages can be flagged to be ignored (i.e. don't trigger PNC builds) is to be decided.