Skip to main content

Setting a time limit for Steps

Abstract

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.

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.

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

    You can edit the file locally, or on the bitrise.yml tab of 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"
In this section:

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.