Tell us how the process of automation of build, testing, and deployment was implemented in your previous projects?

In my previous projects, build, testing, and deployment automation was implemented using CI/CD systems such as Jenkins, GitLab CI, or GitHub Actions. The process typically included the following stages:

1. Build — automatic triggering of the project build on each commit or pull request, using build scripts (e.g., Maven, Gradle, npm).
2. Testing — running unit tests and integration tests to ensure the correctness of changes.
3. Code quality analysis — integration with SonarQube or similar tools to check test coverage and identify issues.
4. Deployment — automatic deployment to test or staging servers, and sometimes to production, using scripts or tools like Ansible, Docker, Kubernetes.

Example of a simple pipeline in GitLab CI:

stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - ./gradlew assemble

test_job:
  stage: test
  script:
    - ./gradlew test
  dependencies:
    - build_job

deploy_job:
  stage: deploy
  script:
    - ./deploy.sh
  when: manual
  dependencies:
    - test_job

This approach allows for quick feedback and minimizes manual errors.