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.
What Invocation Diffing does for you
Mobile builds are complex and often involve dozens of tools, environment variables, and configuration files running across multiple environments. When something suddenly breaks or slows down, it can be difficult to pinpoint the cause. Even a small change in configuration can have a significant impact.
Invocation Diffing was built to eliminate that guesswork.
It helps answer critical debugging questions quickly:
- Why did this command fail today when it passed yesterday?
- Why is this step slower than before?
- What changed between two runs?
Instead of digging through logs or relying on memory, you get a clear side-by-side comparison of two command invocations.
If you spot a performance spike or failure in Bitrise Insights, you can drill down and compare invocations directly from the relevant command. This tight integration ensures faster feedback loops and quicker resolution. What is more, any issue you find can be shared as a link so your colleagues can see what you see.
Available now in Bitrise Build Cache
Invocation Diffing is available to all users of Bitrise Build Cache. If you're already using Build Cache, just open any Invocation Detail page and start comparing.
Changelog
Invocation Diffing in Bitrise Build Cache
Now available in Bitrise Build Cache, the new Invocation Diffing feature allows you to compare two command invocations side by side to quickly identify differences in environment variables, configuration files, machine types, and more. This helps you troubleshoot issues faster, whether you're dealing with build failures or performance regressions.
What’s New
- Compare any two invocations of a command to see exactly what changed
- Identify root causes for:
- Performance regressions
- Unexpected build failures
- Access the feature directly from the Invocation Detail page using the new Compare button
- Fully integrated with Bitrise Insights to investigate issues in depth
