Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

Why Regular IT Health Checks Help Prevent Downtime and Improve Business Resilience

Most IT problems do not announce themselves. A backup job quietly fails for three weeks before anyone notices. A firewall rule left open "temporarily" during a project stays open for a year. A former employee's account still has admin rights nobody remembered to remove. None of these cause trouble on the day they happen. They cause trouble later, usually at the worst possible time. This very difference between when these problems start and when they finally become a source of trouble is precisely what a routine IT health check is supposed to bridge.

Where Test Management Fits in a Modern CI/CD Pipeline

Ask most DevOps teams where testing lives in their pipeline and you'll get a confident answer: "It's automated, it runs on every commit." That's true, and it's also only half the story. Automated checks in CI cover a slice of quality - usually unit and integration tests - but the wider discipline of *test management* often sits outside the pipeline entirely, scattered across spreadsheets, wikis, and someone's memory.

Introducing Harness Agent DLC: Extending your SDLC to AI Agents

Harness Agent DLC: Ship AI Agents to Production Safely Building an AI agent is easy. Getting one into production safely is where teams get stuck. Harness Agent DLC extends the software delivery lifecycle to AI agents, giving teams a clear path to evaluate, deploy, secure, observe, and optimize agents in production. Learn more: Because agents dynamically choose their own tools, APIs, and actions, their behavior can change every time they run. Harness Agent DLC gives engineering teams the controls needed to move beyond experiments and operate agents safely at scale.

Security at Scale: What Changes When Everyone Can Deploy using AI

In our first series post, The New Software Creator, we mapped out a structural shift in the industry: AI is turning non-technical team members into creators of software. In our second post, When Anyone Can Build Software, Deployment Governance Is What Keeps It Safe, we argued that deployment is the single control layer that can secure this explosion of output without choking innovation.

Your AI agents are lost: give them a graph

The biggest limitation facing enterprise AI agents may not be the model. It may be the context surrounding it. Anthony Alcaraz, Senior AI/ML Portfolio Growth Manager at AWS and co-author of O'Reilly's *Agentic GraphRAG*, joins Humans of Reliability to explain why reliable agents need more than a vector database and a large context window. They need structured knowledge they can navigate, memory they can prune, constraints they can follow, and feedback loops that help them improve.

Share packages across your workspace with internal packages

We launched Bitbucket Packages to give teams one place to manage code, pipelines, and artifacts, and we’ve been expanding it ever since, first with Maven and npm, then PyPI and NuGet. Every one of those packages has shared one trait: it lives inside a single repository and inherits that repository’s permissions. Most of the time, that’s exactly what you want. But it also means sharing a package across repositories has meant granting people access to source code they never needed to see.

Cortex Platform Walkthrough

In this video, Becka gives a guided tour of Cortex, the Engineering Operations Platform that runs mission control for your AI software factory. Learn how to centralize visibility, clarify ownership, and automate standards across your entire software ecosystem. What we cover: Why Cortex: Cortex is where engineering leaders run mission control for the AI software factory: the visibility, intelligence, and controls to keep teams shipping fast without letting accelerated output turn into accumulated risk to reliability, security, and cost.

Scanners aren't enough. Here's the layer most teams are missing.

Vulnerability scanners tell you what's wrong with what you already pulled. They don't stop a malicious package from entering your environment in the first place. A private registry with minimum release age policies adds that missing layer – packages newer than two or three days don't reach developers until the industry has had time to identify and remove malicious ones from public registries. Active campaigns like TeamPCP are targeting npm, PyPI, and Maven Central right now. The gate has to come before the scan. Cloudsmith provides that gate.