CI/CD automation steps
An example of the CI/CD automation process is shown in the table below:
| Stage | Description | Tools |
|---|---|---|
| Code Commit | A developer makes changes to the codebase and commits them to the GitLab repository. | GitLab |
| Build | GitLab CI/CD detects the new commit and starts the build process. The build process may involve compiling the code, creating a Docker image, or generating an executable file. | GitLab CI/CD, Docker |
| Test | GitLab CI/CD runs a suite of tests on the built code to ensure that it meets quality standards. This may include unit tests, integration tests, and code quality checks. | GitLab CI/CD, testing frameworks (e.g. Jest, Mocha) |
| Deploy to Staging | If the tests pass, GitLab CI/CD deploys the code changes to a staging environment for further testing and validation. This environment may be a Kubernetes cluster, a cloud provider like AWS or Azure, etc. | GitLab CI/CD, Kubernetes, AWS, Azure |
| Deploy to Production | If the tests pass in the staging environment, GitLab CI/CD deploys the code changes to the production environment. | GitLab CI/CD, Kubernetes, AWS, Azure |