What’s new
You can now view logs generated before the first step of your workflow starts. We introduced a dedicated log section, “Build environment setup,” at the top of the build log view. This section captures:
- Pre-step initialisation: Logs generated while the VM is being prepared (e.g., setting up the agent, checking
bitrise.ymlconfiguration). - Useful information - A summary of some useful information including
den_agent_version,stack_image_version. - Telemetry notices: Information regarding data collection for build insights.
Why this matters
Previously, build failures during environment initialisation weren’t easy to detect. The raw log included information about environment initialisation, but the structured log did not. This used to complicate debugging issues related to tooling dependencies.
This visibility helps debugging “silent failures” where a build crashes before running your first command.
Common use cases:
- Tooling mismatches: If your workflow requires specific pre-installed tools that fail to initialise (e.g., a specific Node.js version required by the CLI), you will now see the error immediately.
- Agent debugging: Verifying which versions of the Bitrise CLI and stack image are actually running.
Who can see this feature:
This feature is enabled automatically for all new builds; no changes to your bitrise.yml are required to see these logs.