cd-flow.md

Continuous Deployment Flow

The majority of the automated steps documented below will be handled by our CI setup detail in the CI Best Practices.

The process below details what process we are aiming for across the group.

Planning

1. Discussion with product owner / stakeholder regarding requirements.
2. Discussion with tester / QA regarding how to test the requirements.
3. For substantial changes schedule a Technical planning meeting.
4. Metric decided for success of code change.
5. Timeframe for success decided.

Code Change

1. The staging branch is checked out on the developer's machine.
2. The latest changes are pulled.
3. A new feature branch is created for the code change.
4. Work is tested locally during development.
5. Commits are created.
6. The new branch is pushed up to GitHub.
7. A new PR is created.
8. Project's contributing document is double checked.
9. Automated tests and quality checks run on project.

Review

1. Work is reviewed by another developer.
2. Work is reviewed by a senior or project guru.

Silo Testing

1. Tester checks out feature branch on their machine.
2. Appropriate testing is performed locally.

Staging (optional)

1. Tester / QA merges feature branch into the staging branch.
2. Changes to staging are automatically deployed to staging environment.
3. Appropriate testing is performed alongside any other recent changes from the team.

Go live

1. Tester / QA merges staging branch into the master branch.
2. Changes to master are deployed automatically to production environment.
3. Minimal automated tests are performed to ensure a successful deployment.
4. Deployment notification sent out to team.

Measure

1. Success of code change is measured by metric and timeframe.