Adopt Minimum Viable CD

[JoeHCQ1]

Overview

As a company, we score potential customers according to the minimumCD rubric and otherwise base ourselves in the CI/CD, DevSecOps tradition. We are only partially in alignment with that tradition right now. Rubric pulled from here: https://minimumcd.org/minimumcd/

❌ Continuous Delivery 50%

• Use Continuous integration 10%
• The application pipeline is the only way to deploy to any environment
• The pipeline decides the releasability of changes, its verdict is definitive
• Artifacts created by the pipeline always meet the organization’s definition of deployable
• Immutable artifact (no human changes after commit)
  All feature work stops when the pipeline is red
• Production-like test environment
• Rollback on-demand
• Application configuration deploys with artifact

❌ Continuous Integration 10%

• Trunk-based development 80%
• Work integrates to the trunk at a minimum daily
• Work has automated testing before merge to trunk
• Work is tested with other work automatically on merge
• All feature work stops when the build is red
• New work does not break delivered work

❌ Trunk Based Development 80%

• All changes integrate into the trunk
• If branches from the trunk are used:
  • They originate from the trunk
  • They re-integrate to the trunk
  • They are short-lived and removed after the merge

[JoeHCQ1]

Cleared dates b/c internal discussions indicate this is not the priority.