A project to demonstrate a deployment pipeline as described in Humble & Farley's Continuous Delivery
(c) Barney Laurance 2021
My plan is to create a minimal PHP web app, and a delivery pipeline to deploy it. The pipeline should as much as practicable faithfully follow patterns and terminology given in sources such as Continuous Delivery by Jez Humble and David Farley, and Continuous Delivery Pipelines - How to Build Better Software Faster by Dave Farley.
A relevant chapter of Continous Delivery is freely available: Continuous Delivery: Anatomy of the Deployment Pipeline.
The pipeline will be run using CircleCI.
Expected problems:
-
What to put in the actual application - needs to be simple enough not to distract too much from the pipeline, but complicated enough to be possible to meaningfully test, and not collect any personally identifiable information for me to be responsible for. Potentially I could compensate for its simplicity by adding some artificial delays to automated checks.
-
How to orchestrate the commit stage - circleCI doesn't seem to offer a nice way to support the pattern given in the books, where only one version is ever being acceptance-tested at any one time, and if many versions pass the commit stage in quick succession only the first and last are acceptance tested, and the in-between versions are ignored.
-
Where to deploy the site to