Summary

During the latest fix build of container images, the version of maven artifacts changed even thought we agreed that this will not be tampered with. The version update and rebuild of maven artifacts was also not announced in the handover, this leads to confusion and uncertainty about the resulting build.
While the images build in CPASS will always be using the latest version available, which are the rebuilt maven artifacts - 00004 suffix. The underlying configuration of some images, spec. builder and devmode, mandates an updated KOGITO_VERSION variable in build scripts. Without the update the latest maven artifacts are not gonna be used.

The above describes the situation we are in after third rebuild of container images. 
During the third try, the environment variable capturing the KOGITO_VERSION was not updated when rebuilding container images and which results in misconfiguration when the images are used in runtime. They use version with suffix - 00003 - to download maven artifacts and other runtime functionalities.

Environment

N/A

Steps to reproduce

1. Deploy workflow into OCP in preview mode
2. Examine the build, it will use 00003 suffix for building, while the image are built with 00004 suffix artifacts.

Actual results

Maven artifacts with version with suffix 00003 are being used in runtime of serverless logic.

Expected results

The scripts are updated and no version with suffix 00003 is being used in runtime of serverless logic.

Testing

We should introduce a smoke test that validates the image runtime environment.