Systems | Development | Analytics | API | Testing

In our recent webinar, we tackled a familiar frustration for many engineering teams: long build times. Our expert panel broke down the problem and explored how remote build caching can deliver faster builds, improved workflows, and real business value. Here are the five biggest takeaways.

During an exciting WWDC25, Apple announced it would skip some numbers and align all OS and software versions to 26. Summer has just arrived, but we’re already keeping our eyes on Apple's usual keynote event in September. The Bitrise team is gearing up for the stable Xcode 26 stack release. We're passionate about providing you with the latest and greatest, and this new Xcode release is no exception. However, we also want to give you a heads-up about what this means for our platform and for our users.

‍Bitrise, the leading mobile DevOps platform, today announced plans to launch a data center in the Netherlands in a response to increased demand for data residency in the European Union (EU). The new data center will be the first in the EU operated by a DevOps Platform, providing businesses with a fully-hosted and managed solution to meet the stringent data security and compliance requirements of the region.

When you think about CI/CD costs, license fees and compute minutes probably come to mind first. But that's just part of the story—especially for mobile. The real cost? Engineering hours lost to fiddly VM maintenance, endless stack upkeep, tooling drift, and waiting on slow builds. This inefficiency hits your bottom line hard, but it's pretty tough to quantify it on a spreadsheet. That’s where the Bitrise ROI calculator comes in.

If you release often or support a localized app, you know how quickly release notes can become a repetitive chore. Creating and managing release notes for every version can take up valuable time, especially when updates are frequent. The challenge grows when your app is localized, but your release notes aren't. App stores typically require localized notes, which often leads to a lot of copy-pasting or scrambling to meet requirements in languages your team may not speak fluently.

Scrolling through the build log to find what caused your CI pipeline to fail isn’t fun. Or even spending hours inventing custom logic to automate workflows based on who triggered a build or what files changed? There might be a better solution. Enhanced Environment Variables have recently arrived – a suite of new variables designed to give you better control over Bitrise CI.

Sometimes teams avoid introducing more tests (particularly UI tests) because they fear slowing down their CI pipeline. Should you have to sacrifice software quality for the sake of fast cycle times? Absolutely not. So, how can you introduce more tests without slowing down your CI pipeline? The answer: employ test sharding. In this post, we’ll dive into what test sharding is and why you should consider it.

Managing multiple apps with different store accounts just got easier. Bitrise Release Management helps developers distribute apps efficiently, whether delivering internal builds or publishing to the App Store or Google Play. It’s built to support teams at scale, with teams relying on it to release hundreds of apps across different platforms and accounts.

Troubleshooting builds just got a lot easier. The new Invocation Diffing feature in Bitrise Build Cache allows you to compare two command invocations side by side to see exactly what changed. Whether you're investigating a build failure or a performance regression, this tool gives you a faster path to understanding and resolution.