[JENKINS-48960] Org folders repository folder never runs scans on repository

Recently updated Jenkins and all available plugins, and the Repository folder within our Organization folder stopped scanning completely. 

 

I went so far as to delete our entire organization structure and re-create it. The organization does scan correctly on changes. The only time the repository level folder scans automatically is upon its initial creation from the creation of the organization. 

 

Also makes little sense that the repository folder has a non-configurable interval of 1 day, while the organization folder was setup with an interval of 5 minutes. This is how the repo's trigger is defined in its config.xml:

H H * * *

86400000

I manually changed that to match the Org folders config trigger, e.g. 

H/12 * * * *

300000

and then gave Jenkins a restart. After ~5 minutes, sure enough, it's now scanning correctly. 

 

So why on earth is the interval timer being set to such a long duration, and so dramatically different than the org's interval timer? 

---
Originally reported by hardwickj, imported from: Org folders repository folder never runs scans on repository

• status: Open
  
• priority: Major
  
• component(s): branch-api-plugin
  
• resolution: Unresolved
  
• votes: 32
  
• watchers: 42
  
• imported: 20251211-141027
  

Raw content of original issue

Recently updated Jenkins and all available plugins, and the Repository folder within our Organization folder stopped scanning completely. 


 


I went so far as to delete our entire organization structure and re-create it. The organization does scan correctly on changes. The only time the repository level folder scans automatically is upon its initial creation from the creation of the organization. 


 


Also makes little sense that the repository folder has a non-configurable interval of 1 day, while the organization folder was setup with an interval of 5 minutes. This is how the repo's trigger is defined in its config.xml:



<spec>H H * * *</spec>

<interval>86400000</interval>





I manually changed that to match the Org folders config trigger, e.g. 



<spec>H/12 * * * *</spec>

<interval>300000</interval>



and then gave Jenkins a restart. After ~5 minutes, sure enough, it's now scanning correctly. 


 


So why on earth is the interval timer being set to such a long duration, and so dramatically different than the org's interval timer? 

• environment: Jenkins 2.101, Folders Plugin 6.3, GitHub Branch Source Plugin 2.3.2

Start by reproducing the repository folder scanning behavior and comparing its config.xml trigger with the parent organization folder's trigger. Verify why the repository interval is set to one day and confirm that repository folders scan automatically at the intended interval without manual configuration edits.

Written by the indexing model from the issue text.