Skip to content

Latest commit

 

History

History
35 lines (28 loc) · 1.98 KB

releasing.md

File metadata and controls

35 lines (28 loc) · 1.98 KB

Releasing

Releasing to non-production

  1. Wait for the Docker build to complete on CircleCI for the feature branch.
  2. Approve the pending staging deployment on CircleCI. Watch the how-to video:
    How to approve staging deployments
  3. 🚨 Unfortunately, our deployment process does not yet fail the build if the deployment fails. To see if the deploy was successful, follow Kubernetes deployments, pods and events for any feedback:
    kubectl --namespace laa-cla-public-staging get pods,deployments -o wide
    kubectl --namespace laa-cla-public-staging get events
    

Releasing to production

  1. Please make sure you tested on a non-production environment before merging.
  2. Merge your feature branch pull request to master.
  3. Wait for the Docker build to complete on CircleCI for the master branch.
  4. Approve the pending staging deployment on CircleCI (see 'Releasing to non-production above' video for more info).
  5. Approve the pending production deployment on CircleCI.
  6. 🚨 Unfortunately, our deployment process does not yet fail the build if the deployment fails. To see if the deploy was successful, follow Kubernetes deployments, pods and events for any feedback:
    kubectl --namespace laa-cla-public-production get pods,deployments -o wide
    kubectl --namespace laa-cla-public-production get events
    

Rolling back

  1. Check the rollout history with kubectl rollout history deployment/laa-cla-public --namespace=laa-cla-public-<environment>
  2. Roll back to the previous version with kubectl rollout undo deployment/laa-cla-public --namespace=laa-cla-public-<environment>

📝 The <environment> above is either staging or production.