Build & deploy
Get an insight on how the project gets tested, built and deployed and the configuration option of the pipeline.
OpenShift Pipelines (based on Tekton) are used as technology for project pipelines. The k5-pipeline-manager is
deployed in the namespace of the Solution Hub and provides the needed pipeline definitions. The pipeline manager is used
by Solution Designer for creating new project pipelines and trigger them. If a new pipeline is created, the pipeline
manager creates a new pipeline and additionally needed pipeline resources to run the pipeline for a specific project.
The project pipeline will create all necessary files, Docker images and Helm charts to deploy, test and run a project
into the k5-project. Each project pipeline is responsible for deploying only one project into its k5-project.
Pipelines types
There are two types of pipelines:
Release pipeline:
The Release pipeline will build the project from the configured Git repository and then publish the Docker image in the OpenShift Registry and the Helm chart in the configured Helm Repository.
Deploy pipeline:
The Deploy pipeline will build the project from the configured Git repository and deploys it to its defined target project.
Task types
Undeploy Solution task:
The Undeploy Solution task is responsible for undeploying a project from the defined target project. It can also clean up used pipeline resources. However, it does not clean Kafka or database resources.
General information
The creation, triggering and deletion of a new pipeline can be done in Solution Designer. The creation of a new pipeline will also trigger the first execution/run of the pipeline. All created pipelines can then be re-triggered in Solution Designer manually. Use the Run button in the CI/CD page in Solution Designer to start a release or a deployment of your project.