Build log grouping: Introducing a new and improved build log feature for mobile app developers

Build log grouping is a new feature that streamlines the build log process, making it easier to understand why a build failed and at which Step the failure occurred. Read how build logs are now grouped by steps, and how we improved our error message display.

We're excited to announce a new feature—build log grouping—that will greatly improve the way mobile app developers build, test, and deploy their apps on our platform. This new feature streamlines the build log process, making it easier to understand why a build failed and at which Step the failure occurred.

Before this update, build logs were often too long and difficult to navigate. Users needed to scroll through the entire log, looking for the failed Step and its corresponding logs. This process was time-consuming and often left developers frustrated. Additionally, many error messages were often brief and cryptic, making it difficult to understand the root cause of the failure.

With this new update, build logs are now grouped by Steps. Finished builds provide logs that are collapsed by default to hide the logs of successful Steps, which are likely to be irrelevant when troubleshooting a failed build. The log of the Step that failed is available immediately, making it much easier to find the error that caused the build to fail.

The collapsed summary also provides information on all the Steps and their timing, which allows developers to easily identify bottlenecks in the build process.

A screen shot of the Bitrise UI for how build logs are grouped.

Bitrise has also made improvements to the way errors are displayed. Error messages are now rolled up and easily accessible, making it quicker to get to the root cause of the build failure. Additionally, we've reviewed the most often failing Steps and redesigned their error messages to provide more detail and context.

Now, when Steps (such as xcode-archive, fastlane, or xcode-test) fail, it will report the phase of the Step where the failure occurred, the command that was executed, and the output the command produced. This way, it is easier to understand whether the issue is in the configuration or the actual execution of the Step.

Overall, this new feature is designed to save mobile app developers time and effort, so they can focus on building great apps rather than troubleshooting build failures. We are confident that this update will greatly improve the developer experience and we look forward to hearing your feedback.

In conclusion, with this new feature, you can now easily find the reason for the build failure, understand the failed Step, and debug easily. This feature makes building, testing, and releasing mobile apps faster, more efficient, and more intuitive. Try it out now and let us know what you think.

Happy building!

The Mobile DevOps Newsletter

Explore more topics

App Development

Learn how to optimize your mobile app deployment processes for iOS, Android, Flutter, ReactNative, and more

Bitrise & Community

Check out the latest from Bitrise and the community. Learn about the upcoming mobile events, employee spotlights, women in tech, and more

Mobile App Releases

Learn how to release faster, better apps on the App Store, Google Play Store, Huawei AppGallery, and other app stores

Mobile DevOps

Learn Mobile DevOps best practices such as DevOps for iOS, Android, and industry-specific DevOps tips for mobile engineers

Mobile Testing & Security

Learn how to optimize mobile testing and security — from automated security checks to robust mobile testing and more.

Product Updates

Check out the latest product updates from Bitrise — Build Insights updates, product news, and more.

The Mobile DevOps Newsletter

Join 1000s of your peers. Sign up to receive Mobile DevOps tips, news, and best practice guides once every two weeks.