[JENKINS-45586] Recent Changes not updated when using GIT Shallow clone option

In a Multibranch job, if the Jenkins File contains the following:

checkout changelog: true, poll: false, scm: [$class: 'GitSCM', branches: [[name: "$\{env.BRANCH_NAME}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: true, reference: '', shallow: +*true*+]], submoduleCfg: [], userRemoteConfigs: [url: '[http://My]]

The "Recent Changes" of the branch will not update.  Previous version (LTS 2.32.1) with old plugins did not had this problem.

Changing the checkout to:

checkout changelog: true, poll: false, scm: [$class: 'GitSCM', branches: [[name: "$\{env.BRANCH_NAME}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: true, reference: '', shallow: +*false*+]], submoduleCfg: [], userRemoteConfigs: [url: '[http://My]]

allows to get the list of "Recent Changes" populated again, but at the cost of a considerably higher build time and stress on the GIT server as the repository need to be cloned from scratch every time (as we are running agents on VMs that are always started from the same snapshot).

 

---
Originally reported by fstlaure, imported from: Recent Changes not updated when using GIT Shallow clone option

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

Raw content of original issue

In a Multibranch job, if the Jenkins File contains the following:


checkout changelog: true, poll: false, scm: [$class: 'GitSCM', branches: [[name: "$\{env.BRANCH_NAME}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: true, reference: '', shallow: +*true*+]], submoduleCfg: [], userRemoteConfigs: [url: '[http://My]]


 The "Recent Changes" of the branch will not update.  Previous version (LTS 2.32.1) with old plugins did not had this problem.


 Changing the checkout to:


 checkout changelog: true, poll: false, scm: [$class: 'GitSCM', branches: [[name: "$\{env.BRANCH_NAME}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', depth: 0, noTags: true, reference: '', shallow: +*false*+]], submoduleCfg: [], userRemoteConfigs: [url: '[http://My]]


allows to get the list of "Recent Changes" populated again, but at the cost of a considerably higher build time and stress on the GIT server as the repository need to be cloned from scratch every time (as we are running agents on VMs that are always started from the same snapshot).


 

environment

```
Jenkins 2.60.1 LTS, all latest plugins on July 17 2017.

Jenkins server running Cent OS and Client running on a Windows Server 2012R2 VM.
```