Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Trunk Based Development - a Case Study
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Samantha Wong
December 21, 2023
22
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Trunk Based Development - a Case Study
This was first shared to the L1T team in GoBusiness on 13 April 2023.
Samantha Wong
December 21, 2023
More Decks by Samantha Wong
See All by Samantha Wong
How Much Testing Is Enough Testing
sshinnee
0
25
The Case for Environment Branching
sshinnee
0
22
Looking for a Content Management System (CMS)
sshinnee
0
30
The World's Ugliest Drawings
sshinnee
0
22
High Fidelity Deployment of Micro-services
sshinnee
0
53
Learning Sessions: Refactoring Reminders
sshinnee
0
49
Learning Sessions: CI/CD
sshinnee
0
26
All About Authentication
sshinnee
0
56
Social and Technical Learnings from A Project
sshinnee
0
95
Featured
See All Featured
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
141
35k
Navigating Algorithm Shifts & AI Overviews - #SMXNext
aleyda
1
1.3k
Code Reviewing Like a Champion
maltzj
528
40k
From Legacy to Launchpad: Building Startup-Ready Communities
dugsong
0
230
Self-Hosted WebAssembly Runtime for Runtime-Neutral Checkpoint/Restore in Edge–Cloud Continuum
chikuwait
0
610
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
123
22k
Deep Space Network (abreviated)
tonyrice
0
210
Money Talks: Using Revenue to Get Sh*t Done
nikkihalliwell
0
260
Leveraging Curiosity to Care for An Aging Population
cassininazir
1
270
GraphQLとの向き合い方2022年版
quramy
50
15k
The #1 spot is gone: here's how to win anyway
tamaranovitovic
2
1.1k
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
apolaine
1
360
Transcript
TBD A GoBusiness Way of Working Samantha Wong - L1T
Sharing Session - 13 April 2023
Table of Contents 1. Standard Deployments 2. Hotfix Deployment a.
First b. Subsequent 3. Clean Ups
6ad7f aaf62 f3854 master
6ad7f aaf62 f3854 v1.0.0 master
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 merge/v1.0.1 git
rebase merge/v1.0.1 on top of master 54843 f3854
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 merge/v1.0.1 git
rebase merge/v1.0.1 on top of master 54843 f3854 merge merge/v1.0.1 into master
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 merge/v1.0.1 git
rebase merge/v1.0.1 on top of master 54843 f3854 merge merge/v1.0.1 into master d1h76
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 merge/v1.0.1 git
rebase merge/v1.0.1 on top of master 54843 f3854 merge merge/v1.0.1 into master d1h76 delete merge/v1.0.1 once merged into master
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 merge/v1.0.1 git
rebase merge/v1.0.1 on top of master 54843 f3854 merge merge/v1.0.1 into master d1h76 delete merge/v1.0.1 once merged into master
6ad7f aaf62 f3854 v1.0.0 master hotfix/v1.0.x 3cd39 v1.0.1 d1h76 delete
merge/v1.0.1 once merged into master