[JENKINS-56059] Branch API should pass the trigger interval to the jobs it creates

We use the "Bitbucket Team/Project" job type to scan for repositories and branches within the repositories.

We rely on periodically scanning for new updates on the repositories and the branches.

Therefore, we would like the created repository jobs to scan for branches at a specified interval.

However, in the branch api plugin the scanning interval is hardcoded to 1 day.

We want the branch api plugin to copy the interval specified in the "Bitbucket Team/Project" job.

We have this feature available in a fork of the branch-api repository.

https://github.com/hvdbrand/branch-api-plugin/commit/56097f900583f82dafb7b25103e745362cdc5698

We would like to deliver this feature to the branch-api-plugin repo.

---
Originally reported by hvdbrand, imported from: Branch API should pass the trigger interval to the jobs it creates

• status: Open
  
• priority: Minor
  
• component(s): branch-api-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251211-141027
  

Raw content of original issue

We use the "Bitbucket Team/Project" job type to scan for repositories and branches within the repositories.


We rely on periodically scanning for new updates on the repositories and the branches.


Therefore, we would like the created repository jobs to scan for branches at a specified interval.


However, in the branch api plugin the scanning interval is hardcoded to 1 day.


We want the branch api plugin to copy the interval specified in the "Bitbucket Team/Project" job.


We have this feature available in a fork of the branch-api repository.


https://github.com/hvdbrand/branch-api-plugin/commit/56097f900583f82dafb7b25103e745362cdc5698


We would like to deliver this feature to the branch-api-plugin repo.

Start by reviewing the linked fork commit and the branch-api-plugin code that creates repository jobs, focusing on where the scanning interval is currently fixed at one day. Trace how the Bitbucket Team/Project job specifies its interval, then verify that created repository jobs inherit it and no longer use the hardcoded value.

Written by the indexing model from the issue text.