The Case for Environment Branching

This was first shared to the GoBusiness team on 20 May 2022.

Transcript

1. CI-CD at Dashboard GoBusiness Share and Learn 20 May 2022 Samantha Wong @sshinnee on GitHub
4. Why do we care? - Ability to work on multiple cards - At different stages/environments of development - Ability to choose which cards go out - Ability to react to production issues @sshinnee on GitHub
5. What are our goals? - Reduce complexity - Production state is the same as states on at least one lower environment - Before: Testing of any state that would go to Production on lower environments - After: Debugging of state that is currently on Production @sshinnee on GitHub
6. A base branching style
7. Maybe a little more features
8. Hmm, we are going to have a release soon
9. Let’s label them
10. Plan for the future
11. Maybe make it simpler
12. As simple as we can
13. Yes, better
14. @sshinnee on GitHub
15. Happy Confluence with our Card Workflow Ready for Dev In Dev Ready for Test In Test Ready for PO Sign-Off Ready for Production Deploy Done dev uat staging prep prod @sshinnee on GitHub
16. Why do we care? - Ability to work on multiple cards - At different stages/environments of development - Ability to choose which cards go out - Ability to react to production issues @sshinnee on GitHub
17. What are our goals? - Reduce complexity - Production state is the same as states on at least one lower environment - Testing of any state that would go to Production on lower environments @sshinnee on GitHub
18. Rather than explicit Release Cycles, the Sprint Cycle is the Release Cycle @sshinnee on GitHub
19. End. Discuss! @sshinnee on GitHub