Azure DevOps pipeline is cancelled when another project is queued

Asked Jun 23 '22 at 14:23

Active Jul 07 '22 at 10:05

Viewed 362 times

This seams to be opposite to problem the majority of people are having.

Basically, we have the default pool with a number of agents listed. A pipeline build is requested and allocated to an agent, an agent is allocated no problem. Once all the agents are processing a pipeline the next pipeline that is requested, won't join a queue. One of the currently active pipelines will be cancelled and the new pipeline is started.

This is not what I would expect, previous build engines queued the new request until an agent became available.

Is there some configuration for this somewhere I have look in the usually places.

Project Settings / Agent Pools
Collection Settings / Agent Pools

Azure DevOps Server 2020

Classic Pipelines

Each requested pipeline is from a different team project and different set of code.

edited Jun 23 '22 at 14:42

asked Jun 23 '22 at 14:23

RickWeb

1,765
2
25
40

1

Post your pipeline YAML. – Daniel Mann Jun 23 '22 at 14:24
@DanielMann I am using classic. – RickWeb Jun 23 '22 at 14:33
Please create a new pipeline with simple definition for a check, will it have same appearance? If not, compare the settings between two pipelines. – wade zhou - MSFT Jun 24 '22 at 09:42
@wadezhou-MSFT two new pipelines, and a new queue, same issue. – RickWeb Jul 08 '22 at 10:03

Azure DevOps pipeline is cancelled when another project is queued

0 Answers0