A glimpse at Runtime
summary
Daily workflow centers on pair programming, mandatory tests-first development and rapid deploys that push every commit through a CI pipeline into a lightweight staging called Tobasco and a larger staging with Diego; an interrupt pair handles community breakages. Specifics: a router change required a backfilled test to catch missing leading-slash routing, a fog gem string-vs-symbol change broke OpenStack and CI flagged it, and red/green CI gates keep the repo safe so fixes and smoke tests validate each deployment.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:05Daily standup and pairing
- 3:11Agile stories and IPM
- 5:21Test-driven development
- 7:31DevOps and deployments
- 8:36Retrospectives and iteration
- 9:18Remote collaboration tools
- 12:11Interrupt pair and support
- 14:40Continuous integration pipeline
- 17:27Cross-environment testing
- 19:12Community contributions
- 21:41Debugging with manifests and logs
- 23:47Pull requests and testing
- 26:16Generalizing solutions
- 27:42Pull request anatomy
- 28:06Q&A session
related talks
33mCloud Foundry Runtime PMC Overview - Dieu Cao, Pivotal
34mAmplifying CI/CD helped Wag! reduce release process by 600%
08mA Year with CF and BOSH
31mPut Your Money Where Your CF Is
44mCloud Native Applications with Remote Development Environments
41mThe Future of Writing Software Happens in CDEs
47mThe Treacherous Trek to Development
03mCore Project Updates Track Introduction