Step-level timeout setting takes precedence over every other timeout setting, be it at node pool-level or system-level. If this value is not set, the step uses the timeout setting configured for the node pool in the UI.
The step-level timeout cannot exceed the timeout set for system or node pool.
The timeout at step-level can be set for any step using the
timeoutSeconds property, which is added to the Configuration section of the step. For more information, see Step Configuration.
In this example, the timeout is set to 300 seconds (5 minutes):
pipelines: - name: my_pipeline steps: - name: my_step type: Bash configuration: timeoutSeconds: 300 //5 minutes execution: onExecute: - echo "This is my step."
Node pool-level timeout is used when one or more steps in your pipeline do not have any timeout specified at the step-level. Each node pool can have a different step timeout duration. Default value is 3600 seconds.
The timeout at node pool-level can be set in the UI. For more information, see Managing Pipelines Node Pools.
Node pool-level timeout cannot be greater than the value set for
System-level timeout is enabled and set to 3600000 milliseconds (60 minutes) by default. This can be set using the
stepTimeoutMS property in the Runtime Configuration section in Pipelines System YAML:
System-level timeout can be changed to any duration of your choice.