• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • remoting
    • None
    • Windows

      I was working with a user yesterday to set up a slave node.
      I granted him all slave permissions (Configure, Delete, Create,
      Disconnect, Connect) and he was able to create the node.

      But it wasn't until I granted him Overall Administer that he was able
      to see the WebStart button in order to start the node (didn't want to
      run as a service because we were experimenting on his localhost.)

          [JENKINS-14610] Full Admin rights needed to run slave WebStart

          A workaround for this is to hack the url of the node to download the jnlp file. Add "slave-agent.jnlp" to the end of the url when you are at the node's page.
          Ex:
          http://<server-name>/computer/<slave-name>/slave-agent.jnlp

          This will download the jnlp file, which is what the Launch button does. Not ideal, but workable.

          Michael Conlon added a comment - A workaround for this is to hack the url of the node to download the jnlp file. Add "slave-agent.jnlp" to the end of the url when you are at the node's page. Ex: http://<server-name>/computer/<slave-name>/slave-agent.jnlp This will download the jnlp file, which is what the Launch button does. Not ideal, but workable.

          Jesse Glick added a comment -

          Jesse Glick added a comment - Was fixed recently: https://github.com/jenkinsci/jenkins/commit/17f0161e56dc2eb213415528061d8c8792694960

            Unassigned Unassigned
            jminne jminne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: