The plugin triggers builds for PRs with same number in different repositories about github-pr-comment-build-plugin HOT 4 OPEN

Definitely not intended behavior. Trying to figure out what is different in your setup though, since we don't hit this problem and we have thousands of PRs across hundreds of repositories.

from github-pr-comment-build-plugin.

Ah, I missed originally that this is for a GitHub Organization Folder job. How did you configure this plugin for the folder? See also #1 as this describes some of what might be involved. Otherwise I think you are the first one (or the first to report) to try this.

from github-pr-comment-build-plugin.

Hello,
Thank you for the fast reply!

In the Jenkins organization folder, we just have the following (relevant?) settings:

I think these are the most relevant ones. I also have "Pull request" event configured in the Github webhook, and if I remove the "Trigger build on PR comment", a build will be triggered if I update one of the PRs, but it will trigger only for the relevant repo.

I had a quick look in the plugin code, as I was looking for the "Triggered build for <...>" source (from the log snippet), and if I interpreted it correctly, it will get all jobs, and if it matches the PR number, and the configured keyword, it will start a build:
https://github.com/jenkinsci/github-pr-comment-build-plugin/blob/fef405665ee23acb44dea17ec12a36a887c58153/src/main/java/com/adobe/jenkins/github_pr_comment_build/IssueCommentGHEventSubscriber.java#L138C42-L138C42

from github-pr-comment-build-plugin.

I believe this is a misconfigured. As mentioned in #1, the trigger must be added in the Jenkinsfile and not on the organization folder itself. I think what is happening (just a guess though without actually seeing the config) is that the folder is the GitHubSCMSource and since it has the property on it, it triggers everything underneath it.

from github-pr-comment-build-plugin.