Tag: CI/CD
DevOps Dozen 2026 Nominations Are Open: Recognizing the People and Technology Moving DevOps Forward
When we launched the DevOps Dozen in 2015, we wanted to recognize the people, projects and companies helping this community move forward. We saw the work happening across DevOps every day at ...
Survey Surfaces Sharp Increase in Amount of Code Written by AI
A global survey of 705 developers and IT leaders finds 42% of respondents reporting that artificial intelligence (AI) now writes at least half their code, with only 21% of developers now spending ...
Git 2.56 Takes Aim at Messy Merges, Slow Diffs and Branch Sprawl
Git 2.56 improves merge safety, speeds up large-repository operations and adds cleanup tools that could prove especially useful for AI coding agents and busy DevOps teams ...
Leaked GitLab Email Tokens Can Reach Code, Secrets and CI/CD Pipelines
Security researchers have uncovered a GitLab behavior that could let attackers use a leaked project email address to push code, trigger CI/CD jobs and reach other repositories accessible to the address owner ...
Dependency Mocking Approach That Gets More Accurate as Your Services Deploy More Often
Traffic-based dependency mocking turns frequent upstream deployments into opportunities to refresh mocks from real behavior and reduce integration test drift ...
Why Old Azure DevOps Releases Survive a Pipeline Cutover
Old Azure DevOps Classic releases can retain retired deployment tasks, Helm names, image paths and variables long after a pipeline cutover, leaving stale redeploy paths active ...
DevSecOps Teams as Partners in Secure Software Delivery
DevSecOps teams can reduce last-minute release delays by shifting security decisions earlier, improving guardrails, clarifying ownership and making findings actionable ...
How I Consolidated Duplicate Delivery Pipelines With Parameters and Build Tags
Two modules in a repository had near-identical Azure DevOps build and release definitions. A third would have required another pair. The delivery chain used five definitions: one change decider, two builds, and ...
Stop Chasing 100% Test Coverage: Why DevOps Teams Need to Test Smarter, Not More
Every software team eventually runs into the same question: How much testing is enough? For years, the default answer has been "more." More automated tests. More regression suites. More environments. More devices ...
GitHub’s August Outages Show Growth Is Outpacing Infrastructure
GitHub's August 2026 report details five outages tied to Actions and Copilot growth outpacing infrastructure. Here's what platform teams should know ...
GitHub Workflows Strain Under AI Agent Development
Coder CEO Rob Whiteley joins Mike Vizard to explain why GitHub workflows, CI/CD pipelines and developer platforms are showing strain under agentic development — and what a policy-aware redesign of the DevOps ...
AI Has Turned Verification Into the New DevOps Bottleneck
The next DevOps challenge is not generating more software. It is proving, quickly and repeatedly, that a growing volume of machine-generated change is fit to ship ...

