Continuous Delivery as a Service
summary
A demo shows creating a continuous delivery pipeline for a Java app by cloning its Git repo, running automated builds and unit tests in the cloud with a Jenkins-style or alternative CI service, and deploying to Heroku so the app is available at a staging URL. The pipeline runs tests on every push, the demo build succeeds, and the setup uses free accounts (no credit card) with an optional paid monitoring add-on.
AI-written summary · about
chapters (15)
- 0:00Introduction to quality in Java
- 2:15Changing roles in software teams
- 5:08Goals of continuous delivery
- 6:34Code repositories and choices
- 9:08Starting a simple Java project
- 10:37Automating builds and tests
- 11:44Alternatives to self-hosted CI
- 12:25Demo: Setting up in CircleCI
- 15:18Deployment automation with Heroku
- 17:25Cloud platforms for deployment
- 18:38Demo: Continuous deployment in Heroku
- 22:22Benefits for all team roles
- 23:46Summary and low-threshold setup
- 27:05Cloud adoption considerations
- 30:33Q&A and closing remarks
related talks
24mWhy, What, and How of Continuous Delivery
47mContinuous Delivery Meets OpenShift
38mContinuous Delivery, or the magic button for on‑demand releases
37mImport Continuous Delivery
41mDevOps for Adults: Live Cooking Show
30mModern Continuous Delivery
42mCONTINUOUS DELIVERY FOR RUBYISTS
55mThe Rationale for Continuous Delivery
