[JENKINS-14855] Repo Build Code Changes not Identified When Job Config is Modified

It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification.

The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log

In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces.

---
Originally reported by rejesi, imported from: Repo Build Code Changes not Identified When Job Config is Modified

• status: Open
  
• priority: Major
  
• component(s): git-plugin, multi-branch-project-plugin (not Pipeline), repo-plugin
  
• label(s): configuration, jenkins, plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 2
  
• imported: 2025-12-02
  

It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification.


The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log


In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces.

environment

```
Linux RHEL server

Linux Ubuntu slave agents

Linux RHEL slave agents

Jenkins 1.472

Repo 1.2.1

Git 1.1.21
```

1 attachment

- [Scan Multibranch.png](https://raw.githubusercontent.com/jenkinsci/attachments-from-jira-issues-last/refs/heads/main/attachments/36120/Scan%20Multibranch.png)
>