Operations | Monitoring | ITSM | DevOps | Cloud

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

GitKraken Desktop 12.4 Release: Multiple WIPs, Approve/Deny Agents, and more!

What if you could counterspell an agent action? GitKraken Desktop 12.4 pulls the whole AI agent workflow into one place, so you stay in the flow. Back in 12.0 we shipped Agent Sessions, where you kick off AI coding agents right inside the context of your repo. GitKraken 12.4 builds on that. What's new in 12.4: This release is not about handing more of your work to agents. It's about seeing everything they do, and deciding what actually changes.

What Is S3-compatible Backup Storage?

A backup is only useful if the data is still there when something goes wrong — and if it can be restored quickly enough to matter. As backup volumes grow, teams need more capacity without losing control of recovery performance or cost. S3-compatible backup storage gives teams another way to handle that pressure. It uses the familiar Amazon Simple Storage Service (Amazon S3) API model without requiring backup data to live in Amazon S3 itself.

Migrate your app to Upsun Cloud without a rewrite

Application migrations stall for a predictable reason: the demanding part is rarely the application code itself. It is the infrastructure around it: the deployment logic, pipeline, and environment configuration that has to be rebuilt. That surrounding work is what turns a migration into a multi-month project, and it is why teams stay on infrastructure that no longer serves them. Upsun Cloud reduces migration to a much smaller task.

Fly Graduates: Agentic Repository Experience Lands in the JFrog Platform

The way software gets built is changing faster than at any point in the last decade, and the software supply chain has to keep up. A year ago at swampUp, we introduced JFrog Fly: the first agentic repository, serving as a fast, AI-native environment to build what a modern, agentic developer workflow could look like, unconstrained by the shape of the enterprise stack. Today, we’re bringing what we learned back home.

Shipped: Give your telemetry streams human-readable names

Telemetry streams carry the unit metrics behind every cost-per-unit number you report. Now each one can say in plain language what it measures. You can call a stream whatever you want to: “MCP tool calls” or “Checkout transactions” or “Documents processed.” Spaces, capitals, and punctuation all work, and you can change the name whenever the metric’s purpose gets clearer. The identifier the pipeline uses stays exactly where it is.