Our journey to automated releases

on YouTube ↗39m

" summary

ABN AMRO moves from Gitflow to trunk based development using feature toggles (they constrain to 11 toggles max) and run a Fastlane-driven CI on Jenkins that runs unit tests, Slather/Xcode coverage, Sauce Labs UI tests on real devices, then builds and disables unfinished toggles before publishing artifacts to Nexus. Static analysis via SonarQube reports metrics (for one app sonarqube shows 28.2% coverage, 587 code smells ≈10 days technical debt, 3% duplication). Assets live in a designer-facing repo with autogenerated enums. Continuous delivery enables bi-weekly — aiming for nightly — releases.

AI-written summary · about

" chapters (26)

1. 0:00Intro
2. 0:57THE APPS
3. 2:02SUMMARY
4. 3:47REAL LIFE GITFLOW
5. 4:34TRUNK BASED DEVELOPMENT
6. 6:15NO FEATURE BRANCHES
7. 7:02STATIC CODE ANALYSIS TO CONTROL CODE QUALITY
8. 7:33HOW TBD HELPS DELIVER FASTER
9. 8:35AUTOMATION
10. 9:20STEPS
11. 10:54UNIT TESTS
12. 13:46SONARQUBE
13. 16:56NEXUS
14. 18:21ALPHA
15. 19:05BETA
16. 20:01SLACK
17. 21:28BUILD MONITOR
18. 23:16FUTURE
19. 25:54WHAT IS IT?
20. 27:30WHAT DOES IT SOLVE?
21. 28:18HOW IS IT USED?
22. 29:28NAMING CONVENTION
23. 31:33SAVE MORE TIME
24. 32:09SETUP
25. 32:41SELECTION
26. 36:10INTEGRATION

" related talks

• 39mOur journey from Gitflow to Trunk Based DevelopmentLudovic Toison · code.talks 2023
• 17mStreamlining Mobile ReleasesEli Budelli · try! Swift NYC 2019
• 57mA continuous fairytaleOda Hoem, Tina Christin Siversen · NDC Oslo 2021
• 01h 01mA team's transition to Continuous DeliveryAshley Noble · NDC Sydney 2017
• 29mOur Journey to Fully Automated Weekly ReleasesMarjana Karzek · droidcon Berlin 2024
• 46mContinuous Delivery for Native AppsNiels Frydenholm · GOTO Copenhagen 2015
• 18mTrunk Based Development and Feature TogglesLeena S N · Agile India 2020
• 01h 12mPitfalls of Continuous DeploymentDavid Cramer · EuroPython 2011