The glob expression that is set up for a trigger is not working correctly.
Common causes & solutions
|You are using a single expression, but are encasing them in curly brackets
Do not encase them in in curly brackets. Instead use
Curly brackets are only used for multiple expressions.
|Incorrect syntax for negation expressions||
|Changed files are in hidden directories||
Glob expressions will not match for hidden directories unless the directory pattern explicitly starts with
For example, to match for all files in all hidden subdirectories immediately under
Note that you will need an additional expression if you want to also match normal subdirectories under
|Incorrect glob expression||
You can check your glob expressions with a tool to ensure the syntax matches the correct files.
|Glob expression is correct; trigger is not starting builds for a different reason||
Try removing the glob expression filter to confirm if that's the source of the issue.
Check your other trigger configs such as event types, target branch, etc.
|Modified file glob expression is not supported for this trigger event type||
Support for specific events can vary between different git providers due to differences in the information they include in their webhook event payloads. Please refer to the documentation on modified files filters.
Support for BitBucket branch push is controlled by feature flags that may be off for your account. Please contact support if you would like to enable this.