Green pipeline. Broken release.
Explore verified evidence from our isolated CI/CD lab. See how failed tests can be ignored, how a controlled pipeline blocks bad code and how digest-verified rollback is demonstrated.
RECORDED SCENARIO 1 / 3
A green build shipped the defect
The simulated pipeline ignored a failed unit test, published mutable latest.zip and checked health only.
Recorded build.log and smoke.json (excerpt)
tests_passed=False
STEP 2: INSECURE POLICY: ignore unit test failure
STEP 3: write mutable artifact named latest.zip
health_gate_passed=True
business_logic_correct=False
RESULT=SUCCESS_WITH_DEFECTA successful job status did not demonstrate release correctness. A failing test had no blocking effect.
Illustrative, fictional lab evidence only. Switching scenarios displays recorded results; it does not execute Jenkins, run code or interact with customer infrastructure. Untested enterprise controls are not assessed.
What would your actual pipelines reveal?
GNU Group offers a fixed-scope, read-only CI/CD reliability assessment of authorised customer evidence. We provide a findings register, prioritised remediation roadmap and management walkthrough. This demo is not a customer assessment or certification.