CI-CD at Dashboard GoBusiness Share and Learn 20 May 2022 Samantha Wong @sshinnee on GitHub 

No content

No content

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 

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 

A base branching style 

Maybe a little more features 

Hmm, we are going to have a release soon 

Let’s label them 

Plan for the future 

Maybe make it simpler 

As simple as we can 

Yes, better 

@sshinnee on GitHub 

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 

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 

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 

Rather than explicit Release Cycles, the Sprint Cycle is the Release Cycle @sshinnee on GitHub 

End. Discuss! @sshinnee on GitHub