From 93c820ca8f47e513e53ceeea59c383aa7ff0096e Mon Sep 17 00:00:00 2001 From: ITViking Date: Fri, 1 Nov 2024 13:21:50 +0100 Subject: [PATCH] fix order of list items --- ...nthly-release-to-editors-and-webmasters.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/runbooks/monthly-release-to-editors-and-webmasters.md b/docs/runbooks/monthly-release-to-editors-and-webmasters.md index 44aa67c2..d9a62c9e 100644 --- a/docs/runbooks/monthly-release-to-editors-and-webmasters.md +++ b/docs/runbooks/monthly-release-to-editors-and-webmasters.md @@ -23,24 +23,24 @@ release - 1. This usually mean last weeks release. 3. Release to webmaster production: 1. Update 'dpl-cms-release' of the 'x-webmaster' anchor to the penultimate version of the CMS. - 4. Commit the change and push your branch to GitHub and create a pull request. - 5. Request a review for the change and wait for approval. - 6. Start `dplsh` from the `/infrastructure` directory of your local + 2. Commit the change and push your branch to GitHub and create a pull request. + 3. Request a review for the change and wait for approval. + 4. Start `dplsh` from the `/infrastructure` directory of your local environment by running `../tools/dplsh/dplsh.sh` - 7. Run `task cluster:mode:release` to get more nodes while deploying. - 8. Run `task sites:sync` from `dplsh` to deploy the changes. - 9. If there are any Terraform changes then do not apply them, abort the + 5. Run `task cluster:mode:release` to get more nodes while deploying. + 6. Run `task sites:sync` from `dplsh` to deploy the changes. + 7. If there are any Terraform changes then do not apply them, abort the deployment and consult the platform team. - 10. Open the Deployments list page within the Lagoon UI to see all running and + 8. Open the Deployments list page within the Lagoon UI to see all running and queued deployments. - 11. Wait for all the deployments to complete. - 12. Run `task sites:incomplete-deployments` to identify any failed deployments. - 13. If some deployments did not complete determine if the error relates to the + 9. Wait for all the deployments to complete. + 10. Run `task sites:incomplete-deployments` to identify any failed deployments. + 11. If some deployments did not complete determine if the error relates to the platform or the application. - 14. For all platform-related errors try to redeploy the environment from + 12. For all platform-related errors try to redeploy the environment from the Lagoon UI. - 15. Merge the pull request once the deployment completes. - 16. Synchronize moduletest with main,so moduletest becomes an exact + 13. Merge the pull request once the deployment completes. + 14. Synchronize moduletest with main,so moduletest becomes an exact copy of main by running `task sites:webmaster:reset-moduletest`. 4. Create a new branch from `main`. 5. Release to editors and webmaster moduletest: