Issue
-
After upgrading Gerrit Plugin to version 2.34, the Jenkins controller becomes increasingly slow and unresponsive and need to be restarted quite often.
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
The Jenkins Test harness jar has been mistakenly included in the version 2.34 of Gerrit Plugin 2.34, which cause a significant memory leak in Jenkins.
The solution is to upgrade the Gerrit Trigger Plugin to version 2.35 or later.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.