Deploy Notes For Next Release

This page should document any additional the steps beyond the usual cap production deploy BRANCH_NAME=master for the next release.

NOTE: Any steps that should be repeated for each release should be integrated into our Capistrano tasks. This page is for one time steps for the next deployment.

Version 3.8

Steps Before CAP

1. verify there is a no-reply email in application.yml

CAP

bundle exec cap production deploy BRANCH_NAME=master

This will also update Ruby to 2.5.5. If you see an error like:

rbenv: cannot rehash: /opt/heracles/deploy/.rbenv/shims/.rbenv-shim exists

Log in to the system and remove the file manually, then re-run the deploy.

Steps After CAP

Cleanup

1. Merge release branch back into develop and delete release branch
2. Notify on Yammer