Details
-
New Feature
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
In order to support non-unix ssh agents and other shells different than bash, we need to implement a way to select different command profiles (bash, PowerShell, ...), this profile will be used by the SSHLauncher to use the proper commands in the proper OS/Shell
Attachments
Issue Links
- is duplicated by
-
JENKINS-57126 Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH
-
- Closed
-
- is related to
-
JENKINS-42856 Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
-
- Fixed but Unreleased
-
-
JENKINS-37152 Support Win32-OpenSSH
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is related to |
Link |
This issue is related to |
Link |
This issue is duplicated by |
I just added a Windows 10 1903 ssh agent to our Jenkins 2.190.2 with ssh-slaves-plugin 1.31.0. There was no need of adding "Prefix Start Agent Command" and "Suffix Start Agent Command" to make it work.