The current CI/CD setup is split by environment. Dev uses webhook-driven deployment and supporting asset publish scripts, while UAT and live use a controlled branch-promotion plus server-side deployment flow.

Overview

flowchart TD A[Code pushed] --> B{Target environment} B --> C[DEV flow] B --> D[UAT/LIVE flow] C --> E[Bitbucket webhook to cPanel] E --> F[deploy.php] F --> G[deploy.sh] G --> H[Optional asset publish to S3 + CloudFront] D --> I[auto_merge.py] I --> J[Environment deployment scripts]

Dev pipeline

In dev, deployment is handled by Bitbucket webhook integration with cPanel. A custom PHP receiver triggers the deployment shell script, and the shell script also sends a Cliq notification after the deployment result is known.

For frontend or static asset publishing, the team also uses a separate S3 + CloudFront batch workflow documented on the S3 & CloudFront page.

UAT and live flow

For UAT and live, branch movement is not push-triggered. The standard order is dev -> test -> uat -> live through auto_merge.py, followed by the relevant environment deployment shell scripts on the server.

!
Manual prerequisites still apply DB changes, environment variable updates, and other environment-specific release tasks must still be handled manually before the final deployment scripts are executed.
PageWhat it covers
Deployment cPanel dev deployment, branch promotion, merge helper, and UAT/live code move steps.
S3 & CloudFront Dev batch script for S3 upload and CloudFront invalidation.