Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64144

Allow Windows JNLP agent connected with websockets to be installed as a service

    XMLWordPrintable

Details

    Description

      When setting up a JNLP agent using websockets and launching the agent using web start on Windows, it doesn't display the File menu containing the 'install as a service' option.

      Enclosed in a screen capture of 2 jnlp agents connected to the same instance.
      The left one is without websockets, the right one has websockets enabled.

      Attachments

        Activity

          ali_alkhazraji Ali added a comment -

          Why there is no update for this feature ? 

          ali_alkhazraji Ali added a comment - Why there is no update for this feature ? 
          foraveragejoe Joe added a comment -

          Is there a workaround at minimum for installing the agent using WebSockets as a windows service?

          foraveragejoe Joe added a comment - Is there a workaround at minimum for installing the agent using WebSockets as a windows service?
          dan33 Zed added a comment -

          jthompson is there any update or workaround regarding this issue? Is there some sort of documentation that explains the reason of why you can't install it as a service when using WebSocket?

          dan33 Zed added a comment - jthompson  is there any update or workaround regarding this issue? Is there some sort of documentation that explains the reason of why you can't install it as a service when using WebSocket?
          jthompson Jeff Thompson added a comment -

          There's no built in workaround or implementation, though there are a number of ways you can roll your own. There are many connection modes with the Remoting library. WebSockets is a new one and no one has implemented the mechanisms to use the "Install as a service" option.

          jthompson Jeff Thompson added a comment - There's no built in workaround or implementation, though there are a number of ways you can roll your own. There are many connection modes with the Remoting library. WebSockets is a new one and no one has implemented the mechanisms to use the "Install as a service" option.
          jglick Jesse Glick added a comment -

          Note that https://jenkins.io/jep/230 proposes to remove the affected functionality from core by default (would still be available as a plugin).

          jglick Jesse Glick added a comment - Note that https://jenkins.io/jep/230 proposes to remove the affected functionality from core by default (would still be available as a plugin).
          karniemi Kari Niemi added a comment -

          It would be at least nice that  this missing option was documented in any of the "marketing" documents for the websocket option. I just spent 2 hours finding out the reason for the missing File menu and "Install as service", and finding the recommended way for installing the websocket-agent as a windows service. There seems to be none referred -even though WebSocket agent is recommended over the JNLP-agent. Any search terms only return legacy documents which are not working for the websocket agent.

          karniemi Kari Niemi added a comment - It would be at least nice that  this missing option was documented in any of the "marketing" documents for the websocket option. I just spent 2 hours finding out the reason for the missing File menu and "Install as service", and finding the recommended way for installing the websocket-agent as a windows service. There seems to be none referred -even though WebSocket agent is recommended over the JNLP-agent. Any search terms only return legacy documents which are not working for the websocket agent.
          dan33 Zed added a comment -

          karniemi could you provide the recommended way for installing the websocket as a windows service?

          dan33 Zed added a comment - karniemi  could you provide the recommended way for installing the websocket as a windows service?
          rkivisto Ray Kivisto added a comment -

          Hi everyone, I came across this issue when working with a CloudBees client who was impacted by this, and I was able to successfully get a WebSocket transport Windows agent installed as a Windows service, and I updated our knowledge base with the solution we used.

          Please see point 2 "Using WebSocket transport and creating the service using WinSW" from:

          https://support.cloudbees.com/hc/en-us/articles/217423827

          rkivisto Ray Kivisto added a comment - Hi everyone, I came across this issue when working with a CloudBees client who was impacted by this, and I was able to successfully get a WebSocket transport Windows agent installed as a Windows service, and I updated our knowledge base with the solution we used. Please see point 2 "Using WebSocket transport and creating the service using WinSW" from: https://support.cloudbees.com/hc/en-us/articles/217423827

          People

            jthompson Jeff Thompson
            vlatombe Vincent Latombe
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated: