Operations | Monitoring | ITSM | DevOps | Cloud

We recently gave you a preview of some exciting changes coming to Bitbucket Pipelines with the release of our next-generation CI/CD runtime. This new runtime will act as the foundation for a range of powerful new future capabilities like ARM and multi-arch builds in cloud, and we're excited to announce that this new runtime is available starting today.

Service level objectives, or SLOs, are a key part of the site reliability engineering toolkit. SLOs provide a framework for defining clear targets around application performance, which ultimately help teams provide a consistent customer experience, balance feature development with platform stability, and improve communication with internal and external users.

Collaboration and communication are critical to the successful implementation of service level objectives. Development and operational teams need to evaluate the impact of their work against established service reliability targets in order to improve their end user experience. Datadog simplifies cross-team collaboration by enabling everyone in your organization to track, manage, and monitor the status of all of their SLOs and error budgets in one place.

In recent years, organizations have increasingly adopted service level objectives, or SLOs, as a fundamental part of their site reliability engineering (SRE) practice. Best practices around SLOs have been pioneered by Google—the Google SRE book and a webinar that we jointly hosted with Google both provide great introductions to this concept. In essence, SLOs are rooted in the idea that service reliability and user happiness go hand in hand.

It’s no secret. Competition is more than fierce in SaaS; it’s also bitter. The competition will enter any market, area, and idea as long as there’s money to fund it — even if the margins are close to zero. Having an observability tool like New Relic or New Relic alternatives can be the key to protecting your margins. A few hours of service disruption, a software bug, or unoptimized code deployment can significantly impact customer experience.

At Cloudsmith, we are excited to announce our support for the Chainguard Registry as an upstream source. By consolidating all your artifacts, packages, and now Chainguard Images into Cloudsmith, your organization can: Integrating the Chainguard Registry as an upstream resource in your Cloudsmith account not only enhances security but also boosts efficiency in your artifact management workflow.

Hello, Bitbucket Cloud Community! We are incredibly excited to announce the introduction of Iterative review, a feature designed to help your team get pull requests completed faster by removing the need to re-review code you've already seen. Now when an author pushes new commits based on your pull request (PR) feedback, you'll have the option to focus on just those new changes.