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, it is marked as failed and the build fails. Steps with Run even if previous Step(s) failed enabled will still run. 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.

1. Find the Step in the bitrise.yml file.

   You can edit the file locally, or in the YAML editor in the Workflow Editor.

2. Add a timeout property before the other Step inputs and specify its value in seconds:

   - [email protected]:
        timeout: 120
        inputs:
        - project_path: "$BITRISE_PROJECT_PATH"
        - scheme: "$BITRISE_SCHEME"