Run SSH Agent using a command on controller Bee Bot July 13, 2022 12:34 Updated The content of this article has moved to the new documentation site. Related articles How to Connect to Remote SSH Agents? Why is the option 'Launch agent by connecting it to the controller' not available How to use the SSH Agent Plugin Kubernetes Plugin: Authenticate with a ServiceAccount to a remote cluster How to access webSockets for Jenkins inbound agents? Comments 2 comments Sort by Date Votes John Seiberling August 25, 2017 18:08 I see that these launch commands have been running on the master for days. It appears they are persistent. Is this the expected behavior or are these threads lingering zombies that should not be present? 0 Steven Christenson June 22, 2018 15:00 I strongly suggest that if using the manual launch method, that additional commands be tossed into the mix.E.g. "env" so you can see what the environment is, "java --version" to be sure the default java is what is expected...And I know John's question is old, but yes, if you use manual launch, it spawns another process that persists for the duration of the connection.We have python based launch mechanisms for our persistent docker slaves (I mean agents :-) that linger. 0 Please sign in to leave a comment.
Comments
2 comments
I see that these launch commands have been running on the master for days. It appears they are persistent. Is this the expected behavior or are these threads lingering zombies that should not be present?
I strongly suggest that if using the manual launch method, that additional commands be tossed into the mix.
E.g. "env" so you can see what the environment is, "java --version" to be sure the default java is what is expected...
And I know John's question is old, but yes, if you use manual launch, it spawns another process that persists for the duration of the connection.
We have python based launch mechanisms for our persistent docker slaves (I mean agents :-) that linger.
Please sign in to leave a comment.