[JENKINS-10336] trigger plugin does not compare paths correctly

Using the "Plain" branch type, if you do a branch named "features/tuner/hit2" (probably anything with two slashes, I would guess), then the Gerrit trigger plugin will never start a job for the branch.

I am using Jenkins version 1.413 and trigger version 2.3.0.

The job is building for one other branch, using "Plain" type, targeted at "master"

This problem can be worked around by changing "Plain" to "Path"

---
Originally reported by bnovc, imported from: trigger plugin does not compare paths correctly

• assignee: rsandell
  
• status: Open
  
• priority: Major
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 0
  
• imported: 2025-12-06
  

Raw content of original issue

Using the "Plain" branch type, if you do a branch named "features/tuner/hit2" (probably anything with two slashes, I would guess), then the Gerrit trigger plugin will never start a job for the branch.


I am using Jenkins version 1.413 and trigger version 2.3.0.


The job is building for one other branch, using "Plain" type, targeted at "master"


This problem can be worked around by changing "Plain" to "Path"

Start by reproducing the issue with a Plain branch named features/tuner/hit2 and a target of master in the gerrit-trigger-plugin. Compare that behavior with the Path branch type; done means the plugin starts the job for the nested branch without requiring the workaround.

Written by the indexing model from the issue text.