[JENKINS-56255] occasionally builds the branch for a PR also

I have a GitHub Organisation configured and it is operating fairly satisfactorily.  It finds PRs when they are opened and builds them, and so on, quite successfully.

But every now and then it will build not only the PR but also the branch that the PR is on, adding a continuous-integration/jenkins/branch commit status to the PR.

This is wasteful in the least a can be confusing to the PR submitters about why they have this strange new commit status occasionally.

I suppose this could happen legitimately if there is latency between pushing to a new branch on GitHub and opening the PR for it.  Is there any delay on building new branches to account for this sort of behaviour?  If not, perhaps there should be?

---
Originally reported by brianjmurrell, imported from: occasionally builds the branch for a PR also

• status: Open
  
• priority: Major
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 4
  
• imported: 2025-12-02
  

Raw content of original issue

I have a GitHub Organisation configured and it is operating fairly satisfactorily.  It finds PRs when they are opened and builds them, and so on, quite successfully.


But every now and then it will build not only the PR but also the branch that the PR is on, adding a continuous-integration/jenkins/branch commit status to the PR.


This is wasteful in the least a can be confusing to the PR submitters about why they have this strange new commit status occasionally.


I suppose this could happen legitimately if there is latency between pushing to a new branch on GitHub and opening the PR for it.  Is there any delay on building new branches to account for this sort of behaviour?  If not, perhaps there should be?

environment

```
Jenkins ver. 2.150.3

GitHub Branch Source Plugin 2.4.2
```

1 attachment

- [image-2019-06-28-07-49-51-334.png](https://issues.jenkins.io/secure/attachment/47813/image-2019-06-28-07-49-51-334.png)
>