-
Bug
-
Resolution: Unresolved
-
Minor
-
None
In main hosting job where all configuration sub jobs are hosted, ssh-agent is started but not getting stopped at the end. It results in ssh-agent process getting leaked on node used for hosting, due to some new features introduced in ssh-agent plugin.
Individual sub jobs are calling both start and stop of ssh-agent but only start is getting called on main job.
- is duplicated by
-
JENKINS-49097 Ssh-agent-plugin doesn't kill ssh-agent in top-level matrix jobs
- Resolved