To ensure smooth and predictable deployments across all environments, please follow the guidelines below whenever requesting a deployment from our team. These steps help maintain proper CI configuration, minimize risks, and support timely debugging if issues arise.
1. Deployment Request Requirements
When submitting a deployment request, always include the following information:
- Branch name
- Pipeline ID
This allows us to verify the correct build and ensures that your branch is properly registered in the CI trigger. If you create or push a new branch, please note that it must first be registered in the CI pipeline before it can be deployed. Inform us early if you plan to use a new branch.
2. Deployment Sequence and Environment Flow
All deployments follow a structured progression to maintain stability across environments.
Sandbox Deployment (Required First Step)
- All deployments must start in Sandbox.
- This is the safest environment for initial validation.
- After deployment, please conduct functional checks to confirm expected behavior.
Staging Deployment
- Once Sandbox testing is completed and confirmed, deployment will proceed to Staging.
- Staging must also be validated before any Production release.
Production Deployment
- Production deployments require both teams to be online and available during the release window for immediate issue resolution.
Production Deployment Scheduling
Production deployments are not performed on Fridays to avoid weekend emergencies when teams may have limited availability.
3. Rollback
We can perform rollback in all environments (Sandbox, Staging, and Production) when necessary. If any build introduces unexpected issues, please notify us immediately so we can initiate a rollback and restore the previous stable version.
4. Best Practices
- Notify us in advance if you expect multiple deployments or the creation of new branches.
- Complete internal QA and build validation before requesting deployment.
- Avoid last-minute or peak-traffic deployment requests unless urgent.