| Page Properties | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| label |
|
Background
1. Where we were:
We had originally no release train, occasional releases on an ad-hoc basis. Devs deployed locally functioning code, through manual steps, till the code eventually reached Stage, where E2E tests were kicked off and POs invited to approve a release of multiple bits of code changes.
We moved to a weekly release train - to Stage - on a Friday (sometimes) which resulted in a release - to Prod - on a Tuesday (sometimes).
The approach was very much a transitional one in advance of a move towards full CI/CD.
This necessitated lots of manual testing which wasn't foolproof fool proof anyway. And a waterfall-style hand-off to Shivani and POs for testing/approval.
There was a very slow pace of development.
The existence of many repos causes difficulties for Devs working across multiple services for one ticket/feature
...
- Panos Paralakis (Unlicensed) : Lead on build up a dependency graph (using POMs and REST calls)
- Simon Meredith (Unlicensed) : Lead on coordinating the move to a mono-repo in Git (can you delegate to someone for your week off, next week, please?)
- Chris Mills (Unlicensed) : Work on integrating failures to a Slack channel (presuming this will require a new Slack channel)
- Chris Mills (Unlicensed) : Work on detecting errors in logs such that they can be tracked and the Dev team / POs can determine whether / when roll-backs need to be initiated
- Oladimeji Onalaja (Unlicensed) : Lead on coordinating getting new pipeline applied to those remaining services (Generic upload, ESR, Reval - others? Chris Mills (Unlicensed) are you able to confirm, please?)
- Shivani Rana (Unlicensed) : Lead on addressing the failing E2E tests. The sooner these can be fixed, the sooner we can then use a correctly failing E2E test as a blocker for build
- Chris Mills (Unlicensed) : Can you add links here for: How to roll-back | (team: is there anything else you want Chris to link to here o clarify the new release approach?)
- Whole team : Work out as soon as possible, an approach to clearing the releases currently awaiting approval, to take away any interference for the team using the new approach