CI/CD

Other technologies

Evidence

• Why this level

  Summary

  CI/CD is implemented repeatedly through GitHub Actions, GitLab CI, SSH deployment, rsync, PM2, lint workflows and quality audits.

• Current ceiling

  Summary

  The main improvement axes to reach the next level are: document more advanced delivery mechanisms, show more infrastructure-as-code, and expose stronger secret-management patterns.

• Automated full-stack deployment

  Permalink Source

  The GitHub Actions workflow in Parking App builds and deploys with container verification and SSH deployment.

• GitLab backend pipeline and PM2

  Permalink Source

  The GitLab CI pipeline in MyHappyWallet industrializes the backend with PM2 deployment profiles for preprod and prod.

• Frontend quality workflow

  PR Source

  The GitHub Actions workflow added in gn_module_monitoring checks both backend and frontend formatting.

• Portfolio CMS deployment

  Permalink Source

  The portfolio CMS triggers SCP copy and then rebuild/restart on a VM at each deployment push.

• Astro site build, deploy and audits

  Permalink Source

  The portfolio frontend automates build/deploy and adds dedicated workflows for Lighthouse, GreenFrame, Ecoindex, ESLint and Prettier.

• GitLab frontend pipeline

  Project Source

  The GitLab CI pipeline documented in the Redux project also covers frontend build and dist artifact publishing.