[JENKINS-29644] Branch parameter ignored when a non-parameterized branch is also monitored

when setting a jenkins job that tracks 2 sources - */develop as jenkins trigger and ${branch} as a parameterized branch

the build always builds the develop branch(as if it was externally triggered) and ignores the ${branch} parameter.

without this option users are forced to create 2+ build jobs doing the same thing, therefor have double the maintenance and bugs because of code duplication

attached the Stash screen that sets up the jenkins trigger

---
Originally reported by roiros, imported from: Branch parameter ignored when a non-parameterized branch is also monitored

• status: Open
  
• priority: Minor
  
• component(s): git-client-plugin
  
• label(s): git, git-client, jenkins, plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 4
  
• imported: 20251211-071809
  

Raw content of original issue

when setting a jenkins job that tracks 2 sources - */develop as jenkins trigger and ${branch} as a parameterized branch

the build always builds the develop branch(as if it was externally triggered) and ignores the ${branch} parameter.


without this option users are forced to create 2+ build jobs doing the same thing, therefor have double the maintenance and bugs because of code duplication


attached the Stash screen that sets up the jenkins trigger

environment

```
git-client 1.16.1

Jenkins 1.580.2
```

1 attachment

- [Screenshot_1.png](https://issues.jenkins.io/secure/attachment/30301/Screenshot_1.png)
>