From 733805e11946718d9a74c2801146fbd30b992ddc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Philip=20J=C3=A4genstedt?= <philip@foolip.org>
Date: Wed, 27 Nov 2019 23:57:17 +0100
Subject: [PATCH] [Azure Pipelines] limit triggers to branches actually used
 (#20441)

Branches like epochs/six_hourly wouldn't do anything, but they create
a lot of entries in the Azure DevOps dashboard:
https://dev.azure.com/web-platform-tests/wpt/_build?definitionId=1

The no-op builds are mostly harmless, but make it harder to find the
interesting builds.
---
 .azure-pipelines.yml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index fa0dc670502745..a534278337d3af 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -16,8 +16,13 @@
 #    https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows
 
 trigger:
-- epochs/*
-- triggers/*
+# These are all the branches referenced in the jobs that follow.
+- epochs/daily
+- epochs/three_hourly
+- triggers/edge_dev
+- triggers/edge_canary
+- triggers/safari_stable
+- triggers/safari_preview
 
 jobs:
 # The affected tests jobs are unconditional for speed, as most PRs have one or