Operations | Monitoring | ITSM | DevOps | Cloud

Let’s imagine, for a moment, that we live in a perfect world. In that world, you could check your company’s cloud bills and financial reports and find cleanly organized categories of spending that help you instantly understand where your money is going and why. Your engineers would meticulously label every spend item with useful metadata tags so you can clearly see which costs have increased and which are most affecting your bottom line.

Over the last few weeks, we’ve launched several new features like support for Docker BuildKit, the ability to set default PR tasks, and fixed a few bugs. Here are the updates.

We are happy to announce that Bitbucket Pipelines now supports non-containerized Linux Shell self-hosted runners. This is currently in beta. You can now create a self-hosted runner and run it on your Linux infrastructure without container restrictions. Since it is your infrastructure, you will not be charged for the build minutes used by your self-hosted runner.

Testing is a vital part of the mobile app development process. Your team can use testing to evaluate the quality, security, and reliability of mobile apps before releasing them to your users. Users who expect their applications to be highly performant and intuitive. There are two ways DevOps teams can perform testing for mobile apps: on-premise (also called self-hosted) or in the cloud. But which of these is the best option for your team?

We’ve reached the point in the DevOps transformation where efficiency and automation are no longer the highest objectives. The next step is engineering past automation and towards fully autonomous, self-healing systems. If you aren’t conversing about building this type of resilience into your systems and applications, there’s never been a better time than now to start.

Implemented well, automation can be a powerful tool for accelerating and scaling DevOps processes to keep your team building and shipping code quickly. But knowing what and how to automate DevOps workflows can be challenging; every organization’s DevOps practices are unique, and there’s no one “right” way to approach automation. Let’s look at a few tips for approaching DevOps workflow automation to help your team move faster.