Setting a time limit for steps

Ensure that your builds do not exceed the time limit by setting up step timeout for steps that might cause builds to hang.

A step timeout, defined in seconds, sets a maximum time a step is allowed to run. If the step exceeds that limit, the workflow moves on to the next step. This is useful if, for example, your builds hang for not immediately obvious reasons - you can set timeouts for the step or steps which are suspected to have caused the problem.

Find the step in the bitrise.yml file.

Don’t forget you can edit the bitrise.yml file of your project on bitrise.io: open the Apps page, select your app, click the Workflow Editor tab then click bitrise.yml.
Add a timeout property before the other step inputs.

Example:

- xcode-test@1.18.14:
     timeout: 120
     inputs:
     - project_path: "$BITRISE_PROJECT_PATH"
     - scheme: "$BITRISE_SCHEME"

And you’re done! In our example, the xcode-test step will abort after 120 seconds. Check the build logs to see what caused the step to exceed the limit.

The configuration format of the Bitrise CLI is referred to as bitrise.yml. This is the expected file name the configuration should be saved with.

Creating your own Step is as simple as running a bitrise CLI (v1.6.1+) command and following the guide it prints. You can generate Steps using either the Bash or Go...

The project scanner is a tool that identifies the given project's type and generates a basic Bitrise configuration. Each supported project type has its own scanner: these scanners are stored...

To understand Bitrise in depth, there are a few key concepts that must be kept in mind. These are immutable and crucial to the way we do things.