Skip to content

Commit

Permalink
[Azure Pipelines] reduce Edge parallel jobs from 20 to 10
Browse files Browse the repository at this point in the history
20 was chosen to make each job of a full EdgeHTML run fast enough, but
with Chromium-based Edge each job now finishes in <1h. Each job has some
overhead, so decrease the number of jobs to 10.
  • Loading branch information
foolip committed Aug 15, 2019
1 parent b16bc55 commit 9ad77ff
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions .azure-pipelines.yml
Expand Up @@ -247,9 +247,8 @@ jobs:
condition: |
or(eq(variables['Build.Reason'], 'Schedule'),
and(eq(variables['Build.Reason'], 'Manual'), variables['run_all_edge']))
# There are 12 agents in the pool, but use more jobs so that each takes <1h.
strategy:
parallel: 20
parallel: 10 # chosen to make runtime ~2h
timeoutInMinutes: 360
pool:
name: 'Hosted Windows Client'
Expand Down Expand Up @@ -283,9 +282,8 @@ jobs:
condition: |
or(eq(variables['Build.Reason'], 'Schedule'),
and(eq(variables['Build.Reason'], 'Manual'), variables['run_all_edge']))
# There are 12 agents in the pool, but use more jobs so that each takes <1h.
strategy:
parallel: 20
parallel: 10 # chosen to make runtime ~2h
timeoutInMinutes: 360
pool:
name: 'Hosted Windows Client'
Expand Down

0 comments on commit 9ad77ff

Please sign in to comment.