The document provides an overview of the CI/CD process for automatic deployments, tests, and load tests in the module repository, highlighting key configurations and workflows. It details the actions triggered by merges, including building images, deployment actions, and maintenance strategies to ensure zero downtime during deploys. Additional warnings regarding potential pitfalls such as GitHub action nesting limitations and Docker Hub rate limits are also discussed.

1. CICD (automatic deploys, tests & loadtests)

2. in the module repo’s
/.github/dependabot.yml

3. From Code to End user.

4. High level overview

5. in the module repo’s PRs

6. in the module repo’s
/.github/workflows/code-sniffer.yml
points to repo with shared
actions

7. The shared action

8. in the site repo PR’s

9. in the site repo PR’s
points to repo with shared
actions

10. The shared action

11. Every merge (commit on master)
Build images
Deploy to TST
Run tests on ENV

13. 13
AUTOMATIC actions
BUILD actions
DEPLOYMENT actions
COMMAND actions

14. 14
Github actions - triggers
✨ Automagic
Nesting can only happen 1 level deep

15. 15
Github actions - triggers
DIY style
Nesting can only happen 1 level deep

16. 16
Workflows
github has them

17. Pitfalls
W
a
r
n
i
n
g
GITHUB NESTING !== NESTING

18. Pitfalls
W
a
r
n
i
n
g
Maintenance POD
- show maintenance page while doing deploys

19. Deploys with zero downtime
Pitfalls
W
a
r
n
i
n
g

20. Docker hub RATE LIMIT
-> FIX 1 : get account on docker hub
-> FIX 2: go to PAID account on docker hub
-> Permanent fix: use Harbour (for container caching on
workers)
Pitfalls
W
a
r
n
i
n
g
OFCOURSE THIS RATE LIMIT HAPPENS ON GOLIVE DAY. GREAT STORY