Per Build Step Chart: Helping you to further shorten build times

Remove bottlenecks. Build great apps faster. With Insights’ build data, know what to prioritise, ship quality code and shift your focus to what matters the most.

Diagnosing issues with your build workflows usually involves an exploration of your build history. Arriving at the correct build issue diagnosis is relevantly easy, and usually involves two steps:

  1. Step 1: Finding the point of influx where your builds started to go wrong, and
  2. Step 2: Finding the variable that caused the builds to block your engineers, at that specific influx point.

The good news is, we recently released two great updates that make it even easier to diagnose your build issues. Helping you to locate your build issues, so much faster. The first is Build time step breakdown, and the second Click-to-zoom.

What we’re introducing today, in line with the suite of aforementioned Insights build features, is making honing in on that build blockers in Step 1, a breeze. We call this the Per Build Step Chart .

What does the Per Build Step Chart do?

The Per Build Step Chart shows the status and duration of individual builds, as well as their constituent step performance. When you now zoom into your workflow performance, you’ll be able to see the most recent builds for the selected time frame.

Figure 1: Zooming in on workflow performance, the most recent builds and their build duration are on display.

This provides you with an overview of the status and performance of all builds, as well as the step that is delaying builds and blocking your engineers. Furthermore, when you hover over an individual step in the chart, the step causing the bottleneck will also be highlighted in other builds it is effecting. Thereby making it easy to compare step performance and get to the root issue of the cause.

Filters in Build History Charts

The Per Build Step Chart also comes with filters. Filters help refine your data, creating subsets for viewing and analysis, helping you to validate what to prioritise. How to use filters?

  1. Filter by build status to identify failing or aborted builds (Figure 2),
  2. Then, chose from
  3. A custom filter for specific steps (Figure 3), or
  4. Builds taking longer than 1 minute to run (Figure 4).

Figure 2: A custom filter for specific steps.

Figure 3: A custom filter for specific steps.

Figure 4: A filter for builds taking longer than one minute to run.

All these features are available today. Hop over to your Insights dashboard and try it out today (Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation).

We continuously aim to help speed up your app development process and build great apps even faster. That’s why more great updates for Insights are on the way. In the meantime, if you have any feedback, please share it with us here.

Happy building!

1 Like