Systems | Development | Analytics | API | Testing

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.

Have you ever wished you could just ask your CI platform a question instead of digging through logs or scrolling through builds? Well your wish has been granted: Bitrise MCP (Model Context Protocol) Server is here, a new, conversational way to interact with your CI.

We know how it feels when a critical build gets stuck in a long queue.