Issue
-
Your Jenkins instance cannot load folders due to out of memory errors.
-
No jobs are showing up in the dashboard.
-
You are getting the below errors in the logs:
SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading item xxx java.lang.OutOfMemoryError: Requested array size exceeds VM limit
Environment
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
-
CloudBees CI (CloudBees Core) on traditional platforms - Client controller
-
CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
Resolution
There was a bug in the Branch API plugin version lower to 2.5.5, which can cause corruption of config file data. This will result in jobs and folders, sometimes even all of them, not loading/showing up in the instance. When this occurs and the data is corrupted, sometimes the only workaround may be restoring from a backup.
However, this issue was fixed in Branch API plugin version 2.5.5. Please refer to this PR for further details regarding this issue.
In order to determine if you have been impacted by this issue, you will need to check the instance logs and confirm if there are occurrences for the below error:
SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading item xxx java.lang.OutOfMemoryError: Requested array size exceeds VM limit
Updating the Branch API plugin to to version 2.5.5 or greater will prevent this issue from happening. That said, if you have already confirmed you are impacted by this, you may need to restore from a backup as mentioned earlier.