Jenkins pipelines play a pivotal role in achieving continuous delivery in software development processes. Continuous delivery (CD) is a software delivery approach aimed at ensuring that code changes are systematically and automatically prepared for release to production. In modern software development practices, CD pipelines streamline the process of building, testing, and deploying software, enabling organizations to accelerate software delivery and provide value to its customers.

As part of the graduation of custom merge checks from open-beta to general availability (GA) that is planned for late-April 2024, we're making a range of changes to several areas of the core Bitbucket Cloud workflow. This includes changes to the core pull request review and authoring experience, as well as changes to how merge checks are configured within a repository. Different changes will be relevant to different audiences, so feel free to use the navigation shortcuts below.

Today, modern software organizations’ requirements for DevOps tooling has become more sophisticated and bespoke. We hear from many customers that they are building large, complex systems to augment and extend their DevOps workflows in ways that don't work well with the tools they're using. This is why Bitbucket Cloud is on a mission to become the world's most extensible cloud SCM and CI/CD product.

A key challenge of monitoring your CI/CD system is understanding how to optimize your workflows and create best practices that help you minimize pipeline slowdowns and better respond to CI issues. In addition to monitoring CI pipelines and their underlying infrastructure, your organization also needs to cultivate effective relationships between platform and development teams.

Ciara Carey reflects on her experience at the KubeCon event in Paris including her top 10 talks and current industry trends.

Last November, Dimitris and Giordano Ricci wrote a blog post about CI/CD observability that looked into ways to extract traces and metrics in order to get a better understanding of possible issues inside a CI/CD system. That post focused on getting data from a continuous integration (CI) system, and it really resonated with the community.