[JENKINS-48666] Gerrit Trigger File Path is unstable.

I have a freestyle jenkins project, and I config the "Gerrit Events" as build triggers. The dynamic configuration userd is as follows:

p=test_project

b=master

f^**/*.java

But I found that if I configured the file path , and push some java files to the gerrit, the gerrit-trigger-plugin will be unstable, sometimes triggered and sometimes not triggered. And I'm sure there's a java file in every event that doesn't tirgger.

If I removed the file path configuration, everything runs normally.

and when I find an event that is not triggered, I wll try to trigger it manually, which can be triggered.

This is a very strange problem that has plagued our team for a few weeks.

 

 

 

---
Originally reported by qeesung, imported from: Gerrit Trigger File Path is unstable.

• assignee: rsandell
  
• status: Open
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 5
  
• watchers: 6
  
• imported: 2025-12-07
  

Raw content of original issue

I have a freestyle jenkins project, and I config the "Gerrit Events" as build triggers. The dynamic configuration userd is as follows:




p=test_project

b=master

f^**/*.java





But I found that if I configured the file path , and push some java files to the gerrit, the gerrit-trigger-plugin will be unstable, sometimes triggered and sometimes not triggered. And I'm sure there's a java file in every event that doesn't tirgger.


If I removed the file path configuration, everything runs normally.


and when I find an event that is not triggered, I wll try to trigger it manually, which can be triggered.


This is a very strange problem that has plagued our team for a few weeks.

 


 


 

environment

```
Jenkins Version: 2.60.3

Gerrit Trigger Plugin Version: 2.27.1

Operation System: Ubuntu 14.04

JDK: Oracle Jdk8
```

No source files or tests are named. Start by reproducing the issue with a freestyle Jenkins project, the Gerrit Events trigger, and the dynamic configuration shown; compare events with and without the file path filter on the listed Jenkins and plugin versions. Done means matching events containing Java files trigger consistently while nonmatching events do not.

Written by the indexing model from the issue text.