FICTIONAL • LAB DEMONSTRATION
CI/CD reliability • evidence-first engineering

Green pipeline.
Broken release.

A controlled GNU Group demonstration showing how a release can appear successful while delivering incorrect business behaviour—and what better release controls look like.

Illustrative demonstration only: All systems, code and outcomes are synthetic. No customer environment was assessed, no production incident was observed, and no certification is implied.
Weak release
GREEN job / FAILED test

One deliberately defective calculation passed into a local simulated deployment because its test failure was ignored.

Unit testFAIL
Health checkPASS
Business outputINCORRECT
Corrected workflow
Block, verify, restore

The same defective version was blocked. Passing versions were identified by content digests, checked after promotion and restored by prior digest.

Defective buildBLOCKED
Artifact integrityVERIFIED
Local rollbackRESTORED

What GNU Group evaluated

1

Build and quality gates

Does a failed test stop promotion, or is failure bypassed in the pipeline?

2

Release identity

Does deployment use an immutable, independently verified artifact?

3

Recovery confidence

Can a previous known-good artifact be restored using recorded evidence?

Evidence-backed example findings

Critical
Failed tests did not block release

Captured nonzero unit-test exit status followed by a simulated release success decision.

High
Mutable artifact tag

The weak workflow deploys a generic latest.zip rather than a content-addressed release.

High
Insufficient smoke coverage

Health was green while an essential business calculation returned an incorrect result.

High
No tested recovery path

The deliberately weak scenario could not restore a previously identified release.

What the demonstration does not prove

It does not evaluate branch protection, real Jenkins agent isolation, production access control, secret management, signed build provenance, network-facing application health, multi-environment promotion, cloud identity or real-world recovery-time objectives. An actual customer assessment would separately seek evidence for these controls.

How GNU Group helps customers

The paid GNU Group CI/CD Reliability Assessment reviews an authorised, defined sample of a customer's actual pipelines and release controls. The outcome is a technical findings register, evidence-adjusted readiness analysis, prioritised improvement plan and management walkthrough.

Explore the assessment

Indicative pilot scope: up to 2 pipelines, 2 repositories, 1 environment. Implementation is quoted separately.

© GNU Group • CI/CD Reliability Demonstration v1.0 • Fictional educational example • Technical observations are local to the demonstration only.