Pipeline Definition for Java Pro-Code Projects

The job mainly follows the build life-cycle basics of Apache Maven. The pro-code project will be validated, compiled, tested by executing the provided unit tests and afterwards packaged in its distributable format.

Creates the Docker image containing the needed denormalized model files for the project and the deploy jobs of the project. The created Docker image will be saved as .tar file, packed in the result image (see pack-installation-image) and then used in the deploy-solution step.

Creates the Helm chart for deploying the project. This Helm chart is packed in the result image (see pack-installation-image) and then used in the deploy-solution step.

Packs the created Helm chart and the project's Docker image (.tar file) into the result image (image name: solutionAcronym:imageTag) and pushes it into the OpenShift registry. That is needed, so the built project artifacts can be used in the Deploy part of a Build & Deploy pipeline and in a Deploy pipeline in another k5-project.

Copies the image (containing the created project image and project's Helm chart) from the configured source (project and image tag) into the current k5-project.

Unpacks the artifacts (created project image as .tar file and the project's Helm chart) from the image (see prepare-image step) and pushes the project image into the current namespace.

It deploys the project to the k5-project using the project's Helm chart. The needed Helm variables for the project deployment (configuration name ssob-sdo-values-yaml) are provided by the Configuration Management (see Solution-Specific Configuration).

Prepares the result image (containing the created project image and project's Helm chart) for the next stage.