Related reading
The Flaky Test Confession: “We All Know We’re Ignoring Test Failures”
Flaky tests silently erode CI reliability, waste compute and developer time, and let real bugs slip into production. The post quantifies the cost (≈2.5 % of developer time, $5.67 per manual investigation vs $0.02 for auto‑rerun) and critiques common band‑aid approaches (retries, quarantine, manual triage). It argues that visibility—detecting flaky tests, predictive test selection, and automated t…
Codeshipcloudbees.com5 minCloudBees Smart Tests Helps Leading Software Company Double Release Velocity by Saving 40K Testing Hours in One Year
The article compares several test‑intelligence products, highlighting CloudBees Smart Tests as a CI‑agnostic solution that allegedly saved a company 40 K testing hours and doubled release velocity. It also outlines the trade‑offs of coverage‑based, ML‑driven, and flaky‑test‑focused tools.
Codeshipcloudbees.com10 minWhen red doesn’t mean broken, your pipeline stops meaning anything
CloudBees Smart Tests adds a “High‑failure‑rate tests” dashboard and a “Quarantine” mode that lets flaky tests keep running but no longer block the pipeline, with manual or automatic thresholds and automatic recovery when failure rates drop.
Codeshipcloudbees.com6 minCloudBees Smart Tests: How AI selects the right tests to run
CloudBees Smart Tests uses GenAI-based semantic analysis to select only relevant tests for code changes, reducing CI runtime by 35-70% and providing immediate feedback. It avoids statistical models, requiring no historical data, and also groups failures and deprioritizes flaky tests.
Codeshipcloudbees.com5 minEvery tool is green. Can you ship?
A CloudBees blog post argues that existing CI, security, and QA tools don’t give release managers a complete view of AI‑generated code risk. It claims tool consolidation rarely helps and proposes a “control plane” (CloudBees Unify) that aggregates signals from multiple tools and adds AI‑driven test prioritization. The piece is largely promotional, with no concrete implementation details, metrics,…
Codeshipcloudbees.com4 minBuilding Multi-Tier CI/CD Verification Gates for AI Pull Requests
AI-generated code often passes basic CI but contains subtle bugs like vacuous tests or off-by-one errors. This article details a multi-tier CI/CD pipeline using AST analysis, property-based testing, and mutation testing to catch these issues and annotate GitHub PRs with actionable SARIF reports.
SitePointsitepoint.com17 min
