GitLab CI/CD - From Zero to Hero

by Nana

https://techworld-with-nana.teachable.com/courses/enrolled/1769488

Nothing really new for me in sections 1, 2 and 3.

• 4 - GitLab Architecture
• 5 - CI-CD pipeline for Node.js Application
• 6 - Optimize CI-CD Pipeline & Configure Multi-Stage Pipeline
• 7 - CI-CD MicroService Application (Mono and Polyrepo)
• 8 - Deploy Microservices to Kubernetes cluster

Things to try at work

• tests generating a JUnit report https://www.npmjs.com/package/jest-junit

• integrate the JUnit report with GitLab's UI https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsjunit

• use the environment keyword in the deploy job https://docs.gitlab.com/ee/ci/yaml/#environment

• use the artifacts:report:dotenv to pass environment variables to the next stages/jobs <

• use cache based on changes in package.json (and/or lock files)

  • depends on removing tests from cloudbuild
  • https://docs.gitlab.com/ee/ci/caching/
  • advanced config.toml configuration: https://docs.gitlab.com/runner/configuration/advanced-configuration.html

• use GitLab's SAST (but with allow_failure): https://docs.gitlab.com/ee/user/application_security/sast/

  • I've noticed in the gl-sast-report.json that some vulnerabilities were found but the job finished successfully.

• deploy jobs should have the name of the environment (dev/stage/us-prod/ca-prod)

Random Notes

Reproduce pipeline locally with Docker compose

While watching Docker for NodeJS course, I had the idea of heaving a docker-compose file for each pipeline job, making it easier to reproduce them locally.

Have a docker-compose-like setup in a pipeline job

• gitlab-ci - running e2e tests on gitlab-runner
• services
• article "e2e test apis using docker and gitlab-ci"