From c97aa9548e3293c677a5c19e212673a1fef69d55 Mon Sep 17 00:00:00 2001 From: Sean-Akin Date: Tue, 20 Oct 2026 12:31:23 +0100 Subject: [PATCH] PLAT-3447: Remove sticky CustomCapabilities pool demand The demand only lets a build run on an agent this repo has already used or on a new VM, never on an idle one, so builds get stuck when the pool is full. Co-Authored-By: Claude Opus 5.5 --- deployment/build.azure-pipelines.yaml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/deployment/build.azure-pipelines.yaml b/deployment/build.azure-pipelines.yaml index c349e42fbd..62dcdc9950 100644 --- a/deployment/build.azure-pipelines.yaml +++ b/deployment/build.azure-pipelines.yaml @@ -32,8 +32,6 @@ parameters: shortCode: intg pool: name: codat-intg-managed-devops-pool-linux - demands: - - CustomCapabilities -equals $(Build.Repository.Name) registryName: codatintgregistry - name: production @@ -45,8 +43,6 @@ stages: - stage: 'build' pool: name: 'codat-intg-managed-devops-pool-linux' - demands: - - CustomCapabilities -equals $(Build.Repository.Name) jobs: - template: Helm/build.frontend.job.yaml@templates parameters: