Issue
This plugin is known to produce a file leak.
You can review the open file handles using:
sudo lsof -p <JENKINS_PID> | grep -c aws-device-farm
Where <JENKINS_PID> is replaced by the Jenkins process id.
Related Issues
- https://github.com/awslabs/aws-device-farm-jenkins-plugin/issues/94
- https://github.com/awslabs/aws-device-farm-jenkins-plugin/pull/92
Environment
- CloudBees CI (CloudBees Core)
- 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
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed controller
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client controller
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- AWS Device Farm Plugin
Resolution
This issue was fixed in version 1.26 of the AWS Device Farm plugin. Please update to the most recent release in order to receive the fix.
0 Comments