What do you think about having one master and no slave configured on Jenkins but having an SSH connection to remote machines initialized in the jobs directly that allow the execution of the build and then, kill the connection instead of creating Jenkins slaves that target the remote machines ?

I ask this question because I would like to avoid Jenkins slave connectivity issues we are facing, especially with Windows remote machines.

Thanks in advance :)

  • We did it on a project, worked fine. However, these days I'd go with Jenkins k8s setup - doesn't have connectivity issues. – taleodor Mar 31 at 12:38
  • Hi, thanks for your reply. Did your machines have Windows ? – V95 Apr 1 at 6:48
  • No, not on that project. – taleodor Apr 1 at 9:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.