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
Don’t forget you can edit the
bitrise.ymlfile of your project on bitrise.io: open the
Appspage, select your app, click the
Workflow Editortab then click
timeoutproperty before the other step inputs.
- firstname.lastname@example.org: 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.
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.
Step inputs are environment items that tell the Bitrise CLI how to run a given step. As discussed in the Steps section, the default inputs can be found in the...