diff options
| author | Tom Rini | 2023-08-20 13:31:26 -0400 |
|---|---|---|
| committer | Tom Rini | 2023-08-28 15:59:22 -0400 |
| commit | 04f7e9538557072500d96447438a4d35f2a64204 (patch) | |
| tree | 21622a178970723ef654ff569b042a041ca4c9c9 | |
| parent | dcde1f95bfa6d634f0cf7b7c0f6f71b3c08c6fa2 (diff) | |
Azure: Set the timeout for jobs to the maximum
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>
| -rw-r--r-- | .azure-pipelines.yml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml index 53a83eef7db..0304be8a60f 100644 --- a/.azure-pipelines.yml +++ b/.azure-pipelines.yml @@ -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) |