# Pattern match trigger branch no longer working

**URL:** https://www.finalbuilder.com/forums/t/pattern-match-trigger-branch-no-longer-working/6028
**Category:** Bugs
**Created:** [February 17, 2016, 4:24am UTC](https://www.finalbuilder.com/forums/t/pattern-match-trigger-branch-no-longer-working/6028 "2016-02-17T04:24:03Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![tony.hoyle](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/t/97f17d/32.png) [@tony.hoyle](https://www.finalbuilder.com/forums/u/tony.hoyle)
#### Post date: [February 17, 2016, 4:24am UTC](https://www.finalbuilder.com/forums/t/pattern-match-trigger-branch-no-longer-working/6028/1 "2016-02-17T04:24:03Z")

</div>

We have a repository trigger that should trigger on any branch ending with the word ‘release’. &nbsp;In previous versions of continua this worked, but as of the current version it has stopped matching.  
  
We’re on version 1.7.1.177 - I’m not sure which version broke as I didn’t notice for a while.  
  
It’s an svn repository with the branch pattern set to trigger on /Branches/\*Release/

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [February 17, 2016, 11:56am UTC](https://www.finalbuilder.com/forums/t/pattern-match-trigger-branch-no-longer-working/6028/2 "2016-02-17T11:56:12Z")

</div>

Hi Tony,  
  
Branch patterns are regular expressions.   
  
The pattern “/Branches/\*Release/” would match “/Branches”, followed by zero or more “/” characters, followed by “Release/”.   
  
You need to use&nbsp;&nbsp;“/Branches/.\*Release/” which would match&nbsp;&nbsp;“/Branches”, followed by zero or more characters ,followed by “Release/”. This would match&nbsp;"&nbsp;/Branches/Release/",&nbsp;“/Branches/V1Release/”&nbsp;&nbsp;or&nbsp;"/Branches/V1/Release/"  
  
Alternatively use&nbsp;&nbsp;“/Branches/[^/]\*Release/” which would match&nbsp;&nbsp;“/Branches”, followed by zero or more characters which are not “/”, followed by “Release/”. This would match&nbsp;“/Branches/Release/”, and “/Branches/V1Release/”&nbsp;&nbsp;but not “/Branches/V1/Release/”
