PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Continuous Code Quality in CI/CD Pipelines

aikido.dev | blog | #devops | #ci-cd | #dora | #alert-fatigue | #code-quality | #quality-gates
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Elite teams ship fast without letting quality slip, yet pipelines battle alert fatigue, rushed reviews, and missing standards. The article examines five obstacles to continuous code quality and fixes.
Published
Collected

Related coverage

blog · about.gitlab.com
How to design GitLab for enterprise scale
A guide to enterprise GitLab rollouts comparing GitLab.com, Dedicated, and self-managed models, with planning guidance for runners, availability, disaster recovery, and pipeline performance at scale.
blog · about.gitlab.com
How to calculate DevOps platform total cost of ownership
GitLab's guide to DevOps platform TCO: beyond license fees, CI/CD compute, AI usage, tooling and staff time all count — model a fixed one-year scope and watch for tool sprawl inflating spend.
blog · wiz.io
The Jenkins Threat Landscape
Wiz data: Jenkins runs in over a third of cloud environments; 59% have instances vulnerable to critical core flaws, 87% contain end-of-life versions, and 48% use highly privileged service accounts.
blog · aikido.dev
Stop breaking SLAs: how to patch vulnerabilities before the fix even ships
Aikido on why teams break vulnerability SLAs: exploitation now tops breach causes as KEV remediation lags, and automated patching can fix dependencies even before upstream fixes ship.
blog · aikido.dev
How to maintain code quality standards with AI code and vibe coding
As AI-written code piles up faster than review can absorb, technical debt compounds until shipping slows; the piece covers pull-request quality checks and why model self-review is not enough.
blog · aikido.dev
How Engineering and Security Teams Can Meet DORA’s Technical Requirements
DORA requires EU financial entities to prove operational resilience with evidence across five pillars. Continuous vulnerability visibility, exploit validation, and resilience testing make it demonstrable.
Back