Build triggered with no regards on BranchFilter parameter at least when used both source and destination as regex

[HamletHakobyan]

Hi,

I have two build jobs on Jenkins which are configured almost identically.
The approachs should be the following:

1. develop-issue-number <- develop-issue-number-impl -- should trigger build job to run unit tests
2. develop <- develop-issue-number -- should trigger build job to create package for feature testing

For the first approach job configured as follows:

1. In the SCM Branch Specifier set to */${sourceBranch}
2. Additional behaviours/Merge before builds

• Name of repository = origin
• Branch to merge to = ${targetBranch}

3. BPRB BranchesFilter set to s:r:^develop-issue-\d+-impl$ d:r:^develop-issue-\d+$

for the second approach job configuration is the same except of point 3
BPRB BranchesFilter set to s:r:^develop-issue-\d+$ d:r:^develop$

When I creating PR for any approaches to build triggers for both jobs.

Is this a bug or I'm doing something wrong.

[HamletHakobyan]

Hi there, someone can take a look on this?

[CodeMonk]

@HamletHakobyan Sorry for the delay. I have just volunteered to be a maintainer.

Does this sill occur? Do you have any updated information about the failure?

[endqwerty]

I'm seeing the same issue. When I have both b: and d: set like b:r:^JIRA-.*-test$ d:staging the regex is ignored. I think it might be doing or instead of and.