Artifactory plugin leaks step arguments

Issue

I have a very slow memory leak due to pipelines being unable to cleanup their previous build data

Environment

CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller (CORE-MM)
CloudBees CI (CloudBees Core) on traditional platforms - Client controller (CORE-CM)
CloudBees Jenkins Enterprise - Managed controller
Jenkins LTS
Artifactory Plugin
Pipeline: Groovy Plugin < 2.59

Jenkins issues

JENKINS-54032

Explanation

Because of the way that the artifactory plugin works, it causes each step argument to leak in memory which ends up holding pipeline executions in memory unable to be garbage collected. The Artifactory plugin creates a pipeline inside of a pipeline and each argument is not correctly cleaned up.

Resolution

With the fix to JENKINS-54032 step arguments are now no longer stored so the fix is to install the Pipeline: Groovy plugin version 2.59 which will fix the leak from happening in the Artifactory plugin

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.