TL; DR: build logs UX is inconvenient so I wrote a userscript to improve my daily work.
Basically, my user journey to find the failure in a build log is the following:
- Click on
Load entire logas the error isn’t visible
- Find the
bitrise-runstep to open it (Usually scroll to the bottom, then up to the
- Find the failing step (Usually scroll to the bottom, then up to the error, or by searching for
| x |that matches the first step failing)
This sounds simple to do, but when you do this a dozen times a day, it is really inconvenient.
The user script automates this workflow to open logs directly on the first failing step.
While pretty, collapsing steps isn’t helpful, and moreover, collapsing the
bitrise-run step, which itself includes substeps isn’t helping either.
One way to improve UX could be:
- Not collapsing steps
- Scrolling automatically to the first error (or through a user action like a button)
As our private git repos are in a private network, we are using a VPN for bitrise to access them.
Because of this all of our workflows are run like this: connect to VPN, clone repo > invoke bitrise-run on workflows declared in the repository.