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 Core
- CloudBees Core on modern cloud platforms - Managed Master
- CloudBees Core on modern cloud platforms - Operations Center
- CloudBees Core on traditional platforms - Client Master
- CloudBees Core on traditional platforms - Operations Center
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed Master
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client Master
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- AWS Device Farm Plugin
Resolution
Uninstalling aws-device-farm
will work around the issue. See https://jenkins.io/doc/book/managing/plugins/#uninstalling-a-plugin.
This Pull Request looks to resolve the issue. At the time of writing there looks to be no associated release.
0 Comments