Overview
Overview
This documentation describes the standard development, release, deployment, and update process for RPA services developed and maintained by the RPA Automation Team.
The goal is to ensure that every service is:
- Developed according to the team's technical standards.
- Tested before release.
- Built and versioned consistently.
- Released in a traceable and repeatable way.
- Configured correctly for each target environment.
- Deployed with the minimum possible number of unexpected issues.
A service release means making an RPA service available on a remote machine, typically using:
- A Docker image published to the repository's internal GitLab Container Registry.
- A Docker Compose configuration.
- Environment-specific configuration.
- Environment-specific secrets.
- Optional external files.
- The automated CI/CD mechanisms available on the RPA infrastructure.
Release lifecycle
Development
↓
Local Validation
↓
Git Commit
↓
GitLab CI
↓
Docker Image Build
↓
Container Registry
↓
Automatic CD
↓
Release VM
↓
Post-Release Validation
The process is divided into two main automated phases:
Continuous Integration — CI
CI is responsible for building and publishing the Docker image.
The CI process is defined by the repository's .gitlab-ci.yml file and is executed by GitLab CI Runners.
See CI – Continuous Integration.
Continuous Deployment — CD
CD is responsible for automatically updating containers running on the RPA Release VMs.
The CD process periodically checks for updated images and restarts the relevant containers.
See CD – Continuous Deployment.
No Comments