This is a an open-ended question, and if there's a better place to post it just let me know.
I have a large amount of selenium tests that I want to run using Jenkins. Currently, I have Jenkins running the selenium grid plugin and therefore functioning as the hub, and a Windows VM running the selenium server as node that I access using remote desktop (Jenkins runs in linux, and I need to test with IE, so I can't use the Jenkins box as the node). I tried to run the selenium server as a service, but that didn't work (apparently you can't do that).
So, I currently have a command prompt perpetually open while logged in to the VM as myself. I'm not a fan of this solution, as it's reliant on a command prompt staying open and me always logged in. But I can't seem to find a better solution, nor can I even find anything on best practices regarding long-term use of the node.
screenyou can disconnect and close the terminal window and reconnect to it later so your "con" is not a problem at all. Will that answer your concern?