Deep Dive: DotNet and CF Pipeline
summary
A concrete CI/CD pipeline builds .NET Core, runs unit and integration tests, publishes ~199 artifact files once, then the release pipeline programmatically creates a Cloud Foundry space, uses non‑interactive CF CLI auth, pushes the build, creates and binds services (MySQL and a config server), and starts the app; the demo deploys to dev, succeeds, and pauses for manual QA approval. Local workflow uses Docker Compose for local service stubs and Swagger, and build gating enforces coverage and integration tests. Azure DevOps and Cloud Foundry drive the automation.
AI-written summary · about
chapters (11)
- 0:00Introduction and speakers
- 1:52Agile process overview
- 4:22Decomposing with event storming
- 8:40Git branching and development
- 10:56Team enablement strategies
- 17:33DevOps pipeline introduction
- 18:40DotNet Core benefits
- 21:33CI and CD pipeline setup
- 36:32Live demo walkthrough
- 53:43Q&A session
- 56:52Key takeaways and summary
related talks
10mCloud Foundry Accelerates "DevOps+"
22mLet's Build A CI CD Pipeline
56mAzure DevOps for .NET Teams
33mMigrating .NET and .NET Core to Pivotal Cloud Foundry
27mBuilding powerful DevOps pipelines with Microsoft Azure DevOps
07mIntroduction to the Cloud Foundry for Developers Track
32mCloud Foundry for Everyone!
28mImprovements to the .NET Developer Experience on Cloud Foundry