Installing a windows slave is currently looking like knight fight!

      JNLP looks like the simplest solution, but we can't rely on this solution to setup automatically slaves with scripts and turn Jenkins as a service. There are many pittfalls with rights, registry tricks and .net FW or java security...

      The jenkins-slave.exe is not reliable at all neither... to do the job.

      We definitively need a much better slave installation method that allows scalable and scriptable slave installation without asshole. There are plenty of sofware who does this for years, so I don't understand why Jenkins can't!

      Jenkins is not only used in Linux world!!!
      Thanks community.
      A desperate Windows user.

          [JENKINS-37173] Windows Slaves unattended installation

          Oleg Nenashev added a comment -

          Well, creating "_unsorted" feature request is not the best way to provide feedback. I do monitor bugs only. If you have particular WinSW issues, please report them here: https://github.com/kohsuke/winsw

          Now you can consider creating Docker slaves on Windows, etc.

          Oleg Nenashev added a comment - Well, creating "_unsorted" feature request is not the best way to provide feedback. I do monitor bugs only. If you have particular WinSW issues, please report them here: https://github.com/kohsuke/winsw Now you can consider creating Docker slaves on Windows, etc.

          Oleg Nenashev added a comment -

          Closing as Not a defect (not a particular one). Guidelines are provided to the user

          Oleg Nenashev added a comment - Closing as Not a defect (not a particular one). Guidelines are provided to the user

            oleg_nenashev Oleg Nenashev
            fredericmeyrou Frédéric Meyrou
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: