Azure: Set the timeout for jobs to the maximum
authorTom Rini <trini@konsulko.com>
Sun, 20 Aug 2023 17:31:26 +0000 (13:31 -0400)
committerTom Rini <trini@konsulko.com>
Mon, 28 Aug 2023 19:59:22 +0000 (15:59 -0400)
As per current Azure Pipelines documentation we qualify for 3600 minutes
per job, if specified, as the timeout. The default unspecified timeout
is 60 minutes. Rework things to specify 0 as the timeout (and so maximum
allowed) so that we don't have failures due to running slightly past 60
minutes total.

Link: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml#timeouts
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
.azure-pipelines.yml

index 53a83ee..0304be8 100644 (file)
@@ -468,6 +468,7 @@ stages:
 - stage: world_build
   jobs:
   - job: build_the_world
+    timeoutInMinutes: 0 # Use the maximum allowed
     displayName: 'Build the World'
     pool:
       vmImage: $(ubuntu_vm)