[JENKINS-47515] Pipeline rebuilds commits which have already passed without stating why

Currently at the last passing build of master, pipeline-github/job/core/job/master/44/

I can see that it has successfully built revision 29e70493c0598970cc10aa60134ce72739bc938d.

A few hours ago Jenkins kicked off master/45. If I look in the console log for the new build, it says:

```
Obtained Jenkinsfile from 29e70493c0598970cc10aa60134ce72739bc938d
```

This looks like the same commit to me, so I'd like the plugin to explain why it's rebuilding something which is already known to be green. We can't have builds doing this unnecessarily, because there are almost 100 pull requests which haven't merged yet because they haven't been able to fully build due to various other Jenkins issues. (In the meantime, I'm going to have to manually kill it... but now the status is going to be grey...)

What we know:

• Nobody kicked it off manually (Status would show the name of the user who did it)


• The configuration didn't change from the previous build (we are using a plugin which shows an icon if that occurs)

---
Originally reported by trejkaz, imported from: Pipeline rebuilds commits which have already passed without stating why

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

Raw content of original issue

Currently at the last passing build of master, pipeline-github/job/core/job/master/44/


I can see that it has successfully built revision 29e70493c0598970cc10aa60134ce72739bc938d.


A few hours ago Jenkins kicked off master/45. If I look in the console log for the new build, it says:




Obtained Jenkinsfile from 29e70493c0598970cc10aa60134ce72739bc938d



This looks like the same commit to me, so I'd like the plugin to explain why it's rebuilding something which is already known to be green. We can't have builds doing this unnecessarily, because there are almost 100 pull requests which haven't merged yet because they haven't been able to fully build due to various other Jenkins issues. (In the meantime, I'm going to have to manually kill it... but now the status is going to be grey...)


What we know:




	
Nobody kicked it off manually (Status would show the name of the user who did it)

	
The configuration didn't change from the previous build (we are using a plugin which shows an icon if that occurs)

• environment: Jenkins 2.85, GitHub Branch Source 2.2.3, GitHub 1.28.0, Pipeline 2.5, Pipeline: Multibranch 2.16

3 attachments

- [Screen Shot 2017-10-26 at 9.19.43 am.png](https://issues.jenkins.io/secure/attachment/40124/Screen%20Shot%202017-10-26%20at%209.19.43%20am.png)
> 
- [Screen Shot 2017-10-26 at 9.20.12 am.png](https://issues.jenkins.io/secure/attachment/40125/Screen%20Shot%202017-10-26%20at%209.20.12%20am.png)
> 
- [build-cause.gif](https://issues.jenkins.io/secure/attachment/40089/build-cause.gif)
>