|
|
| Line 42: |
Line 42: |
| * Demo to PO | | * Demo to PO |
| * Testers deployed to production during twice daily release windows | | * Testers deployed to production during twice daily release windows |
|
| |
| ==Deploy Process at Trade Me==
| |
| :The deploy process is where a story completed on a feature branch is deployed to production, the deployment of stories is shepherded by the testers, with active support from the platform team and the story's developers.
| |
| :* The completed feature branch is merged into the integration branch (at any time) and then promoted to a test environment and tested.
| |
| :* Most weekdays there are are two, two hour deploy windows. Just prior to the start of a deploy window, a release candidate is built from the head of the integration branch. This batches up all the integrated change sets since the last deploy. The release is promoted to, and tested in, the stage environment.
| |
| :* The release candidate is then deployed to production and errors actively monitored for a short period of time.
| |
| :* Once the deploy is confirmed, the release is merged to the default trunk of the code.
| |
| :At times multiple components need to be deployed, and the sequence of deploying these is important.
| |
| :During the steps above, the testers are responsible to monitor, and make a number of checks, to ensure the new build is good to be deployed to production. If an urgent issue occurs the deploy lead can chose to rollback or to ask the squad to do a hot fix.
| |
| :I have deployed new stories routinely and been a test deploy lead many times at Trade Me.
| |
|
| |
|
| ==Tools used at Trade Me== | | ==Tools used at Trade Me== |