[JENKINS-72652] New github org folder always enables child health metrics

Our Jenkins servers started having blocked/deadlocked threads due to Cloudbees Folder Health Metrics as we run on AWS ECS and EFS (NFS) for Jenkins home directory.

We followed this doc on disabling Health Metrics:

How to disable the weather column to resolve instance slowness? (cloudbees.com)

We still had some blocked/deadlocked systems coming not from regular folders but from the GitHub Branch Source plugin (Github Org Folder).   

We removed all of the Health Checks from the Github Folder but still had some controllers get in the same blocked/deadlock situation.   

We then removed any ChildHealth Metrics settings but discovered that if we delete the "Child item with worst health" property, it would come right back after saving the change.

We then tried to uncheck the "Recursive" checkbox but that too would get checked again whenever a Github Org Scan would run.

Is there an easy way to just totally disable and Health Metrics/Child Health Metrics on github branch source folders?

We find the weather information of little value as people only want to know if the last build was red or green.  Is there some easy way to disable this permanently.

---
Originally reported by johnlengeling, imported from: New github org folder always enables child health metrics

• status: Open
  
• priority: Minor
  
• component(s): cloudbees-folder-plugin, github-branch-source-plugin
  
• label(s): deadlock
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-02
  

Raw content of original issue

Our Jenkins servers started having blocked/deadlocked threads due to Cloudbees Folder Health Metrics as we run on AWS ECS and EFS (NFS) for Jenkins home directory.


We followed this doc on disabling Health Metrics:


How to disable the weather column to resolve instance slowness? (cloudbees.com)


We still had some blocked/deadlocked systems coming not from regular folders but from the GitHub Branch Source plugin (Github Org Folder).   


We removed all of the Health Checks from the Github Folder but still had some controllers get in the same blocked/deadlock situation.   


We then removed any ChildHealth Metrics settings but discovered that if we delete the "Child item with worst health" property, it would come right back after saving the change.


We then tried to uncheck the "Recursive" checkbox but that too would get checked again whenever a Github Org Scan would run.


Is there an easy way to just totally disable and Health Metrics/Child Health Metrics on github branch source folders?


We find the weather information of little value as people only want to know if the last build was red or green.  Is there some easy way to disable this permanently.

environment

```
Jenkins Controller 4.426.3

github-branch-source: 1752.vc201a_0235d80

cloudbees-folders: 6.858.v898218f3609d

Jenkins controllers running under AWS ECS

Jenkins home directory running on AWS EFS
```