CD processes

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.

1. EDP flow

1.1. Library

This simple CI process involves creating a jar file and publishing it in Nexus.

edp lib pipeline

1.2. Application

In addition to the library, the application enables you to deploy a Docker image and publish it in the registry. Each application is deployed using the Helm chart located in the deploy-templates folder.

edp application pipeline

2. Development environments

2.1. DB and API for template services integration

template cd

3. Jenkins agent

jenkins image

4. Registry deployment (target)

target cd

5. Verification of changes

The final artifact that will be delivered is the dataplatform-jenkins-agent. Any changes made to one of the components must be integrated and verified in conjunction with others.

The agent consists of verified versions:

  • service-generation-utility

  • DB service structures (procedures, historical tables, and so on)

  • liquibase-ddm-ext

  • blueprint-generator

Verification takes place in the Dockerfile.

Steps to deploy a new version of the data factory:

  • Build the modified artifact.

  • Update the version in the Jenkins agent (Dockerfile).

  • Wait for the artifact to be built.

  • Update the agent version in the Jenkins ConfigMap operator key: dataplatform-jenkins-agent-template.

  • Wait for the build to finish.

  • Deploy the Jenkins operator to the development environment.

  • Deploy the registry by committing the regulations to Gerrit.

  • Verify that the changes work properly (dev. testing).