summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSven Boemer <sbomer@gmail.com>2018-12-18 21:09:58 -0800
committerGitHub <noreply@github.com>2018-12-18 21:09:58 -0800
commitc0c51f83e56eb37bb5a257c0e82ca6676894d6c1 (patch)
tree096354a7e7bbcfd22a77d25ea5442841d66b92b1
parentf80fc46282cf2ff53483eb5c1483ba26880fb8b8 (diff)
downloadcoreclr-c0c51f83e56eb37bb5a257c0e82ca6676894d6c1.tar.gz
coreclr-c0c51f83e56eb37bb5a257c0e82ca6676894d6c1.tar.bz2
coreclr-c0c51f83e56eb37bb5a257c0e82ca6676894d6c1.zip
Add build timeout (#21591)
This should fix official build failures that are timing out because the jobs are waiting to obtain an exclusive lock on the blob feed.
-rw-r--r--azure-pipelines.yml5
-rw-r--r--eng/build-job.yml4
2 files changed, 9 insertions, 0 deletions
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 0aba334b60..a0ab3eb4b5 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -110,6 +110,11 @@ jobs:
parameters:
jobTemplate: build-job.yml
buildConfig: release
+ jobParameters:
+ # Publishing packages to blob feeds sometimes takes a long time
+ # due to waiting for an exclusive lock on the feed.
+ # See https://github.com/dotnet/arcade/blob/master/Documentation/CorePackages/AsyncPublishing.md
+ timeoutInMinutes: 120
#
# Checked test builds
diff --git a/eng/build-job.yml b/eng/build-job.yml
index 064db098ed..24c7de8907 100644
--- a/eng/build-job.yml
+++ b/eng/build-job.yml
@@ -5,6 +5,7 @@ parameters:
osIdentifier: ''
containerName: ''
crossrootfsDir: ''
+ timeoutInMinutes: ''
### Product build
jobs:
@@ -23,6 +24,9 @@ jobs:
# Run all steps in the container.
# Note that the containers are resources defined in azure-pipelines.yml
containerName: ${{ parameters.containerName }}
+
+ timeoutInMinutes: ${{ parameters.timeoutInMinutes }}
+
crossrootfsDir: ${{ parameters.crossrootfsDir }}
gatherAssetManifests: true