Designing a CI/CD pipeline developers will not route around
A pipeline succeeds when it is fast enough to trust and strict enough to matter. Getting that balance wrong is why teams disable checks.
Topic
Every article we have published on devops.
A pipeline succeeds when it is fast enough to trust and strict enough to matter. Getting that balance wrong is why teams disable checks.
Four measures describe delivery performance well. They are useful for finding constraints and harmful when used to compare teams.
Credentials in repositories remain one of the most common causes of breach, and it is one of the most preventable.
Progressive delivery limits how many users a bad release can reach. The mechanism matters less than having a rehearsed way back.
An internal platform succeeds when using it is easier than not using it. Mandates without ergonomics produce workarounds.
Most post-mortem processes produce documents nobody reads. A few practices make them produce actual change.
GitOps gives auditable, reversible deployments by declaring desired state in version control and letting an agent reconcile it.
Most container vulnerabilities come from what you did not need to include. Reducing the image is the most effective single control.
Most production-only failures trace to a small set of differences between environments. Closing them is cheaper than debugging the consequences.