A team's transition to Continuous Delivery

on YouTube ↗01h 01m

" summary

Team cuts build+deploy time from days to about an hour and reaches 22 deployments a day with three to production, by adopting trunk-based CI, automated acceptance tests and a formal pipeline. Pipeline uses Bitbucket, Bamboo, Artifactory, Octopus + LaunchDarkly and SpecFlow for executable specs; deployments become single‑click releases with immutable configs. QA roles shift into DevOps as tests gate releases; acceptance suite runs ~1 hour (workarounds for Azure AD throttling add delays). One manual 24‑hour production gate remains.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 24:55Octopus Deploy
3. 32:12Automated Acceptance Tests
4. 33:26Execution times
5. 35:37Transient Failures in AATS

" related talks

• 47mContinuous Delivery WarstoriesAllan Ebdrup · GOTO Copenhagen 2015
• 01h 26mOptimising Continuous DeliveryDave Farley · Agile India 2023
• 30mOur Continuous Delivery JourneySuzie Prince · DevOpsDays Kansas City 2016
• 28mClimbing the Mountain of CI/CD: A Tester’s TaleMichele Campbell · UtahJS Conf 2018
• 33mContinuous Delivery Pipelines: How to Build Better Software FasterDave Farley · GOTO Copenhagen 2021
• 28mMinimum Viable Continuous DeliveryBryan Finster · Global SRE Virtual Conference 2022
• 54mFrom Code to CustomerTobias Mende · NDC Porto 2024
• 05mBuilding an end-to-end DevOps pipelineKutay PEKŞEN · DevOpsDays Istanbul 2019