Operations | Monitoring | ITSM | DevOps | Cloud

If you’re like most developers, you know that writing code isn’t the bottleneck anymore. AI has made it faster than ever, and chances are you’re already using it. Yet, delivering software is still complex because of everything else you have to manage: fixing vulnerabilities, reducing tech debt, cleaning up feature flags, ensuring test coverage, writing documentation, and the list goes on. That’s why we built Rovo Dev, a context-aware AI agent for developers.

When we first introduced the JFrog AI Catalog, it was our mission to provide the industry with a single system of record for governing the complex landscape of internal, open-source, and external commercial AI models. This foundational step was critical for enterprises to move from uncontrolled innovation to delivering AI with trust and confidence. However, the AI landscape is ever-evolving. The challenge for today’s enterprise is already evolving beyond simply managing a library of known models.

A fundamental shift in software development is already here. Gartner predicts that by 2028, 75% of enterprise software engineers will use AI code assistants – a massive leap from less than 10% in early 2023. While this AI-driven speed creates a competitive advantage, it also opens a dangerous new front in the battle for software supply chain security.

The backbone of modern software development is automation and at the heart of that lies the CI/CD pipeline. It’s what turns code into deployable software, delivering changes to users faster, safer, and more predictably. In simple terms, a CI/CD pipeline automates everything from the moment developers push code to when it reaches production. It integrates, tests, builds, and deploys software continuously ensuring faster releases with fewer human errors.

The Playwright framework is known for its UI testing features, but it also has robust tools for testing API capabilities. Playwright API testing tools allow you to build faster and more reliable end-to-end tests. Because you can combine both the UI and API tests into one test suite, your testing efforts become more efficient.

Deploying web apps can feel overwhelming. Multiple moving parts, including frameworks, hosting, databases, and automation tools make having a smooth, automated workflow seem impossible. But having an automated workflow is worth the effort; you can focus on building features and improving your app instead of worrying about manual deployments or server management.

OpenTofu has emerged as the true open successor to Terraform, restoring transparency and community ownership after Terraform’s shift to a restrictive BSL license. With features like OCI registries, encryption at rest, and a public RFC process, it’s already outpacing Terraform’s innovation.

Until recently, the Pipelines Billing Panel has only displayed the total pipeline minutes used across your workspace. You didn’t have visibility into how usage was distributed across your repositories. We’ve now enhanced the billing panel to show you build minute usage by repository for the current and previous billing periods so you can identify and manage high-usage repositories.

TypeScript introduces the benefits of static typing to JavaScript, allowing developers to identify bugs at an earlier stage. However, relying solely on developers to run type checks locally isn’t enough. Without tsc being called, a person can just leave the invalid code and it may pass to production. This tutorial will show you how to set up CircleCI to automatically run the TypeScript type checks on each push.

The speed and reliability of deploying backend and full-stack applications are usually a concern for development teams. Fortunately, Railway is a developer-friendly platform that allows you to deploy apps with limited configuration. It is also quick, easy to use, and has reasonable defaults. Now, imagine pairing that with CircleCI, one of the strongest continuous integration platforms available.