Skip to content

Latest commit

 

History

History
29 lines (18 loc) · 1.66 KB

03-how-to-deploy.md

File metadata and controls

29 lines (18 loc) · 1.66 KB
Raw

How to deploy

Your pull request is ready, all comments made by reviewers have been addressed and CI results (Teamcity) are green. Congratulations, you can deploy your code to production. Here are the steps to do so:

Deploying

The Guardian frontend uses Continuous Deployment, any code pushed to the main branch would be automatically deployed to production

  1. Merge your pull request to main 1a. Wait for the tests and build to finish (Teamcity)
  2. Once the build step is completed, it will be automatically deployed to PROD. 2a. Prout will send a notification when the deployment has completed
  3. Verify that your change works properly. 3a. Check the Deploy dashboard (Private) for any potential issue.

Blocking deployment

In order to prevent anybody to deploy you can block deployment. To do so, add a restriction in Riff-Raff (Private) for dotcom:frontend-all and the stage you want to lock (PROD or .* for all stages).

Delete the restriction to unblock deploys.

Frequently asked questions

  • When something goes wrong during deployment, a service cluster might be left in an inconsistent state (ie: running servers count doesn't match the expected count) Developers would need to fix this inconsistency before to start any subsequent deploy (a consistency check is done as the first step of a deploy so all successive deploys will fail until this is resolved). To do so, you can modify the expected number of instance for a given Autoscaling group using the AWS console or goo tool (ex: ./goo groups update AUTOSCALING-GROUP-ID 3 3 12)