From 40861c7c698d7c1a570500ab98a096d39bdc3ef8 Mon Sep 17 00:00:00 2001 From: Steve Danielson Date: Tue, 31 Aug 2021 11:17:25 -0400 Subject: [PATCH] Wildcards for continuous deployment triggers --- docs/pipelines/release/triggers.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/pipelines/release/triggers.md b/docs/pipelines/release/triggers.md index 4c143d5787c..30b225ed6c1 100644 --- a/docs/pipelines/release/triggers.md +++ b/docs/pipelines/release/triggers.md @@ -6,7 +6,7 @@ ms.topic: tutorial ms.author: ronai author: RoopeshNair ms.custom: seodec18, contperf-fy21q1 -ms.date: 09/25/2020 +ms.date: 08/31/2021 monikerRange: '>= tfs-2015' --- @@ -36,6 +36,8 @@ Continuous deployment triggers allow you to create a release every time a new bu Build branch filters allow you to trigger a release only for a build that is from one of the branches selected here. +A release will be triggered only if the Git push contains a commit on the specified branch. For example, selecting `main` will trigger a release for a Git push which contains one or more commits to the main branch. To trigger a release for any commit to branches under `features/`, enter `features/*`. To trigger a release for commits to all branches, enter `*`. Note that all specified filters will be OR'ed. For example, an artifact matching at least one filter condition would be sufficient to trigger a release. + You also have the option to specify branch tags. If you do so, a release will be triggered only if a new build tagged with the keywords specified here, is available. > [!NOTE]