Tag: CI/CD
Coding Agents Broke Git’s Scaling Math. GitHub Is Rebuilding to Keep Up
Tom Smith | | agentic AI, AI coding agents, automation, Azure Blob Storage, CI/CD, code review, developer productivity, devops, GIT, Git Infrastructure, github, GitHub Actions, platform engineering, Repository Scaling, software development, software engineering, Trunk-Based DevelopmentGitHub is rebuilding its Git infrastructure as AI coding agents drive billions of commits, promising up to 35x faster writes while exposing new DevOps bottlenecks ...
DevOps Has Always Been Hard to Define. Does a Standard Help?
Alan Shimel | | agentic AI, AI agents, AI Governance, automation, CI/CD, devops, DevOps governance, devops institute, devops maturity, DevOps practices, DevOps standard, DORA, ITIL 5, observability, OWASP agentic AI, PEOPLECERT, platform engineering, software delivery, software engineeringThe new DevOps Standard deserves a serious reading. Its lasting value will depend on whether it helps organizations apply shared principles as people and agents take on different responsibilities ...
Federated Query at Petabyte Scale: A Deployment Pattern for a Governed AI-Agent Data Layer
Pavan Gatadi | | AI agents, AI Governance, CI/CD, data architecture, data governance, data products, devops, distributed SQL, enterprise data, enterprise GenAI, federated query, HIPAA, kubernetes, MCP, observability, regulated data, role-based access control, semantic layer, Starburst, Terraform, TrinoA federated query architecture can reduce data duplication and latency while creating a governed, auditable data layer that enterprise AI agents can safely access ...
Security Teams Are Fixing Vulnerabilities Faster Than Ever. So Why Is Software Getting Riskier?
Mitchell Johnson | | AI coding agents, AI Development, application security, automated remediation, CI/CD, dependency security, dependency selection, developer experience, devsecops, open source security, secure coding, secure software development, security policy, shift left security, software composition analysis, software risk, Software Supply Chain, technical debt, vulnerability backlog, vulnerability managementAI is speeding up dependency decisions, making point-of-selection security essential for reducing vulnerable components, downstream tickets and avoidable rework ...
Taste, Discernment, and Judgment Have Become Must-Have Engineering Skills
Gautam Korlam | | AI code review, AI coding agents, AI-generated code, autonomous coding, autonomous merge, CI/CD, code quality, code review, deterministic systems, developer productivity, devops, engineering judgment, engineering standards, human judgment, pull requests, quality gates, software architecture, software engineering, software governance, technical debtAI coding agents make code generation cheap, shifting engineering value toward standards, deterministic quality gates, contextual review and human judgment about what should ship ...
Open Source Mod Brings Rate Limits, Costs and CI Status Into View for Claude Code Users
Tom Smith | | agentic AI, AI coding agents, AI costs, AI Governance, AI observability, Anji Xu, CI/CD, Claude Code, Claude Statuspane, context windows, developer productivity, developer tools, devops, GitHub Actions, platform engineering, token usageClaude Statuspane gives developers real-time visibility into Claude Code context use, rate limits, costs and CI status, highlighting a growing need for agent observability ...
DevOps Dozen 2026 Nominations Are Open: Recognizing the People and Technology Moving DevOps Forward
Alan Shimel | | agentic AI, AgentOps, AI software development, CI/CD, developer productivity, DevOps 2026, DevOps awards, devops dozen, DevOps Dozen Awards, devsecops, FinOps, internal developer platforms, LLMOps, MLOps, observability, open source, platform engineering, software delivery, Software Supply Chain SecurityWhen 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
Tom Smith | | AI coding agents, CI/CD, coding agents, developer tools, devops, GIT, Git 2.56, Git performance, Git repositories, merge conflicts, monorepos, platform engineering, software development, source control, version controlGit 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
Jaime Hampton | | Aikido Security, application security, CI/CD, devsecops, gitlab, Software Supply ChainSecurity 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
Sancharini Panda | | API testing, CI/CD, Contract Testing, Dependency Mocking, devops, ebpf, integration testing, Keploy, microservices, Mock Drift, service virtualization, software testing, test automation, Testcontainers, Traffic-Based MockingTraffic-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
Ahmed Tariq | | Azure DevOps, Azure DevOps Classic, Azure pipelines, CI/CD, container security, deployment automation, devops, devsecops, Helm, kubernetes, Kubernetes security, Pipeline Migration, release management, Release Pipelines, software deliveryOld 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 ...
