[JENKINS-76324] Keep a history of the `file-descriptors.txt` for future reference

`file-descriptors.txt` can be helpful for troubleshooting the file descriptor leak. However, by the time the controller process runs out of file descriptors it is impossible to generate a new support bundle. It'd be great if the support bundle generated after the restart included a handful of `file-descriptors.txt` files leading up to the incident.

---
Originally reported by duemir, imported from: Keep a history of the `file-descriptors.txt` for future reference

• assignee: escoem
  
• status: Open
  
• priority: Minor
  
• component(s): support-core-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

`file-descriptors.txt` can be helpful for troubleshooting the file descriptor leak. However, by the time the controller process runs out of file descriptors it is impossible to generate a new support bundle. It'd be great if the support bundle generated after the restart included a handful of `file-descriptors.txt` files leading up to the incident.

Start by locating how the support bundle generates `file-descriptors.txt` and how bundle data is retained across controller restarts. Define the retention window for a handful of historical files, then verify that a post-restart support bundle includes the files leading up to the incident.

Written by the indexing model from the issue text.