[JENKINS-49703] Pipeline GitHub Changelog No Changes on Merge

We have a pipeline set up for a GitHub repo with a Jenkinsfile. On a merge from a pull request, a build will trigger but it will not always pick up changes (the "Changes" link on the build is empty). After some more commits/merges are added, all of the changes since the last build that had changes will get picked up, so no commits are actually missed, but it takes a few to actually get picked up.

I would expect every new build that is building on a new revision would pick up the changes. Is this not how the plugins work? Or do we have something set up wrong? In our Jenkinsfile we are using shared library code that is both in a different repo and in the same repo as this Jenkinsfile, so we have `library 'myrepo@${branch}'` (for dynamic loading if the build is on a PR instead of master) as well as some Groovy source code being loaded with `@​Library('myrepo@​master')` since without it, the source code does not appear to be added to the classpath (removing this causes `unable to resolve class` errors).

The attached screenshots are two screenshots of one build that has an empty "Changes" page and only 1 (duplicate) "Git Build Data" that should have picked up changes to the branch. The other screenshot is of the build that came directly after it that has more "Git Build Data" and had all of the changes that were missed by previous builds that should have had changes.

---
Originally reported by dustinchaloupka, imported from: Pipeline GitHub Changelog No Changes on Merge

• status: Open
  
• priority: Minor
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 4
  
• watchers: 7
  
• imported: 2025-12-02
  

Raw content of original issue

We have a pipeline set up for a GitHub repo with a Jenkinsfile. On a merge from a pull request, a build will trigger but it will not always pick up changes (the "Changes" link on the build is empty). After some more commits/merges are added, all of the changes since the last build that had changes will get picked up, so no commits are actually missed, but it takes a few to actually get picked up.


I would expect every new build that is building on a new revision would pick up the changes. Is this not how the plugins work? Or do we have something set up wrong? In our Jenkinsfile we are using shared library code that is both in a different repo and in the same repo as this Jenkinsfile, so we have `library 'myrepo@${branch}'` (for dynamic loading if the build is on a PR instead of master) as well as some Groovy source code being loaded with `@Library('myrepo@master')` since without it, the source code does not appear to be added to the classpath (removing this causes `unable to resolve class` errors).


The attached screenshots are two screenshots of one build that has an empty "Changes" page and only 1 (duplicate) "Git Build Data" that should have picked up changes to the branch. The other screenshot is of the build that came directly after it that has more "Git Build Data" and had all of the changes that were missed by previous builds that should have had changes.

environment

```
git-client-plugin 2.7.1

git-plugin 3.7.0

Jenkins 2.89.4
```

3 attachments

- [Screen Shot 2018-02-22 at 1.19.11 PM.png](https://issues.jenkins.io/secure/attachment/41576/Screen%20Shot%202018-02-22%20at%201.19.11%20PM.png)
> 
- [Screen Shot 2018-02-22 at 1.19.32 PM.png](https://issues.jenkins.io/secure/attachment/41575/Screen%20Shot%202018-02-22%20at%201.19.32%20PM.png)
> 
- [Screen Shot 2018-02-22 at 1.19.48 PM.png](https://issues.jenkins.io/secure/attachment/41574/Screen%20Shot%202018-02-22%20at%201.19.48%20PM.png)
>