githubEdit

How to handle failed deployments and revert changes in Moodle

Context During a Moodle deployment, you may encounter failures that require immediate attention, particularly when database updates or post-deployment scripts fail to execute properly. This can happen due to database query issues or instance reachability problems. Answer When encountering deployment failures, follow these steps to diagnose and resolve the issue: Check the GitHub Actions logs for specific error messages in the deployment pipeline Verify instance health status in your cloud console: Confirm system reachability checks are passing Ensure instance reachability checks are successful Validate EBS status checks If instance health checks are failing: Restart the affected server Wait for health checks to return to "Ready" state For database-related deployment failures: Review the error messages in deployment logs Check SQL query syntax in post-deployment scripts Ensure database queries are properly formatted for multiple row operations (use IN clauses instead of = for subqueries that may return multiple rows) After fixing any identified issues: Ensure code changes are pushed to the correct branch Re-trigger the deployment action Monitor the deployment for successful completion If you need immediate assistance with deployment issues, contact the support team through your designated support channel.

Last updated

Was this helpful?