Increase cancelTimeoutInMinutes
This is a setting AZDO supports to control how long you have after a
build is canceled before all of the work is terminated.
When a build reaches a timeout, usually the `build.{cmd|sh}` step will
be terminated, and then you have cancelTimeoutInMinutes number of
minutes to do everything else before everything shuts down.
We need to a value larger than the default of 5 minutes because it takes
us *about* 5 minutes to upload all of our logs and artifacts in a
success case.
This should give us a sufficient grace period to upload all of our logs
in the case that a build fails due to a test hang.
This commit is contained in:
parent
7b6654d164
commit
706309f266
|
|
@ -69,6 +69,11 @@ parameters:
|
||||||
installJdk: true
|
installJdk: true
|
||||||
timeoutInMinutes: 180
|
timeoutInMinutes: 180
|
||||||
|
|
||||||
|
# We need longer than the default amount of 5 minutes to upload our logs/artifacts. (We currently take around 5 mins in the best case).
|
||||||
|
# This makes sure we have time to upload everything in the case of a build timeout - really important for investigating a build
|
||||||
|
# timeout due to test hangs.
|
||||||
|
cancelTimeoutInMinutes: 15
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
- job: ${{ coalesce(parameters.jobName, parameters.agentOs) }}
|
- job: ${{ coalesce(parameters.jobName, parameters.agentOs) }}
|
||||||
displayName: ${{ coalesce(parameters.jobDisplayName, parameters.agentOs) }}
|
displayName: ${{ coalesce(parameters.jobDisplayName, parameters.agentOs) }}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue