Tell us about the CI/CD pipeline: what environments, what steps, how was the process built?

The CI/CD pipeline is usually built from several stages and environments:

1. Environments:

   • Development (dev) — for initial testing and integration of new features.
   • Staging — for integration testing and verification before release.
   • Production — for releasing a stable version.

2. Pipeline steps:

   • Building the project.
   • Running unit tests.
   • Static code analysis (lint, security checks).
   • Deploying to the dev environment.
   • Integration and e2e tests.
   • Manual or automatic approval for deployment to staging.
   • Testing in staging.
   • Automatic deployment to production after successful completion of all tests.

3. Process:

   • Code is pushed to the repository, triggering the pipeline.
   • All steps are executed sequentially with status notifications.
   • Tools like Jenkins, GitLab CI, or GitHub Actions are used.

Example configuration for GitLab CI:

stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - go build -v ./...

test_job:
  stage: test
  script:
    - go test -v ./...

deploy_dev:
  stage: deploy
  script:
    - ./deploy.sh dev
  only:
    - develop

deploy_prod:
  stage: deploy
  script:
    - ./deploy.sh prod
  when: manual
  only:
    - master

This approach allows automating the code delivery process and minimizing human errors.