Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Labels:None
-
Environment:Jenkins 2.263.2
Windows 10 1909 64-bit
-
Similar Issues:
Description
We are currently running Jenkins agents in VirtualBox VMs on the master. We are investigating running agents on Windows Sandbox for a built-in lite VM that allows GUI testing.
I've tried "Launch agent via execution of a command on the master", but this appears to only work when that commands results in stdin/stdout of the agent being connected. This isn't possible with Windows Sandbox unless we got some sort of hacky reverse shell working somehow.
We'd like Jenkins to run a command to start the VM/Sandbox then connect back via JNLP or WebSockets, but as far as I can tell these two launch methods are mutually exclusive.
Do you have any further information about what errors or messages you see?
I'm not familiar with any issues like this, so we would need to identify the cause and make sure we understand what would need to be done.