Expand/collapse build logs per step within a Bitrise Run step

Feature Requests Builds
1

Description of the feature request

The logs generated by the Bitrise Run step (and all the workflows run subsequently) are collapsed in a single section on the build log page.
It would be nice to have them separated by step.

Before:

+ Step 1
+ Step 2
+ Bitrise Run step
   Step 3
   Step 4
+ Step 5

After:

+ Step 1
+ Step 2
+ Bitrise Run step
   + Step 3
   + Step 4
+ Step 5

Use case / for what or how I would use it

We use Bitrise Run steps quite a lot. This feature would improve our experience navigating our build logs.

2

Thanks for the #feature-request @philippebb! For anyone interested, I want to point out that with hosting the .yml in the repository this is achievable, but there are certain use cases the Bitrise Run step works better with, so the request is still appreciated!

3

As a matter of fact we have both: a yml on bitrise.io with a Bitrise Run step that calls a workflow defined in a yml in our source code repo.
In the example from my original post:

  • Step 1, 2 and 5 are defined in the yml on bitrise.io
  • Step 3 and 4 are defined in the yml in our repo
4

Please can we get this feature. We run a single giant bitrise run step and the logs are insane to parse

5

@philippebb @fred.ells and anyone using “Bitrise run” step :rocket:
We are working on something awesome, but we still need some feedback on this step.
We’d love to hear more about your experiences in this 1-minute survey: https://bitrise.typeform.com/to/wp3ItWpJ

Thank you! :purple_heart:

6

Any updates on this? We would greatly appreciate something like this as we share build logic via common.yml’s and host the main-part of the workflow inside our project repository.

The workflow config inside bitrise.io only includes the triggermap to prevent build runs at all if the conditions are not met and downloading some common files from our private git repository used by the main workflow.

Several reasons force us to do so, e.g.:

  • source control via git and history for changes

  • better ways of sharing, reusing and maintaining workflow steps and scripts

  • pullrequests with reviews on workflow changes

currently it looks something like this as we use ‘bitrise run’ inside a script step:

image
image353×309 13.6 KB

Any way to visualize that sub-workflows better would be much appreciated.