Story

CI scripts refer to all the bash files located in .ibm/pipelines. These scripts handle setting up the cluster, deploying RHDH using Helm chart and Operator, running the tests, and cleaning up. These scripts differ for different cluster types, such as OCP, AKS, GKE, etc. The main difference is between OCP and all the K8s clusters.

As a maintainer of the CI jobs, I want to be able to:

• Minimize failures caused by errors in deployment.
• Easily investigate failures caused by the CI scripts.
• Be able to easily extend our deployments and tests for new functionalities and cluster types.
• Unify how tests are skipped and targeted only for specific clusters/install methods.

Background

• have code deduplicated
• use a unified method of creating Secrets and ConfigMaps, probably with the use of envsubst command where needed
• have extended logging to allow easier debugging of failures, while keeping the sensitive information hidden
• have the utils.sh broken down into smaller files
• rewrite Bash functions to use local variables instead of global ones, which allows the check for unpopulated variables
• add checks for the population of global variables
• unite the `namespace` and `project` variables into one (presumably `namespace`), keep the project where it is relevant as OCP specific
• unify the configuration through value files and app-config between OCP and K8s and Helm chart and Operator. Ideally, configure it in one place and have it for all (e.g. env vars) where possible.
•  

CI jobs should be refactored, so that the folder structure is based on platform (OCP, K8s - AKS, GKE, ...), install method (Helm and Operator), pull or nightly, ...

We can use Bats to generate JUnit files that can be passed to ReportPortal. That way we get the full picture in ReportPortal reports.

Dependencies and Blockers

QE impacted work

Documentation impacted work

Acceptance Criteria

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo