Plugin does not work with MultiBranch Pipelines

[jsj1027]

Current trigger setup:
triggers{
bitbucketpr(cron: '* * * * ',
credentialsId: '',
repositoryOwner: '',
repositoryName: '**',
branchesFilter: '/${sourceBranch}
branchesFilterBySCMIncludes: true,
ciKey: 'jenkins.pr',
ciName: 'jenkins.pr',
checkDestinationCommit: false,
approveIfSuccess: true,
buildChronologically: true,
cancelOutdatedJobs: true,
commentTrigger: 'test this now')
}
Current Behavior:

Currently if you setup the a Jenkinsfile for a MBP(MutliBranchPipeline) with this plugin you get very weird behavior.

Lets say you have branches A,B,C with open PRs.
But only branch A has the Jenkinsfile for the MBP. This triggers a build on the MBP in the branch A section for builds A B and C.
The descriptions of the builds will be whatever the PR name was for each branch respectively.

Then lets say you do a scan of the MBP, this will trigger builds for A,B,C in the branch A section, with the same outcome as above. This can be stopped by turning off index triggers.

Now lets say you make branch D, with a open PR, but this one also has the new Jenkinsfile for the MBP.
This triggers a build in the branch A section rather than the branch D section.

Now if you run a build manually in the branch D section of the MBP this triggers builds for A,B,C,D.

Expected Behavior:

Pull Request triggers only fire off builds for their respective branches in only their respective sections.
Branch D triggers only create builds in the branch D section.
Only branch A triggers create builds in the branch A section.

Branch indexing triggers, if turned on, only fire off builds for the branches that have the Jenkinsfile in their respective sections.
Builds would happen in the branch A, and D sections respectively, but only for branches A and D.

Screenshots and further clarification available upon request.

[jsj1027]

Anyone able to help with this?

[nickheyer]

Why do these clearly broken plugins exist in Jenkins....

[jsj1027]

No idea.

…

On Tue, Nov 19, 2024, 2:50 PM Nicholas W. Heyer ***@***.***> wrote: Why do these clearly broken plugins exist in Jenkins.... — Reply to this email directly, view it on GitHub <#241 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGG47G2XNLF4SMBEWXCM7VD2BOJANAVCNFSM6AAAAABSC5VCICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGYYTEOJVGQ> . You are receiving this because you authored the thread.Message ID: <nishio-dens/bitbucket-pullrequest-builder-plugin/issues/241/2486612954@ github.com>