[JENKINS-76277] Rate limit during org folder/multibranch scan leads to repos/branches being deleted

When the branch source plugin hits the gitlab rate limit when doing indexing, the project/branch it was scanning then gets ignored and dropped from Jenkins, this then requires another scan to bring it back, but all the build history is then also lost as a consequence.

---
Originally reported by jonsey, imported from: Rate limit during org folder/multibranch scan leads to repos/branches being deleted

• assignee: baymac
  
• status: Open
  
• priority: Minor
  
• component(s): gitlab-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251216-182730
  

Raw content of original issue

When the branch source plugin hits the gitlab rate limit when doing indexing, the project/branch it was scanning then gets ignored and dropped from Jenkins, this then requires another scan to bring it back, but all the build history is then also lost as a consequence.