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

File context menu missing when installing Slave under windows with jnlp

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Environment:
      Windows Server 2012
      Windows 7
      Jenkins LTS 1.580.3
      Java 7u51
      Java 8u31
    • Similar Issues:

      Description

      In the provided version of Jenkins I am not able to install jenkins slaves as windows services because the file context menu is missing when lauching the slave.

      I tried all combinations of the above mentioned software versions.

      I cannot give more information because there is no log output anywhere. The conext menu is only missing...

      Hope you can help or tell me what information you need to solve that problem.

      EDIT:
      I tested same OS/JAVA combinations with Jenkins LTS 1.565.3 and everything works as expected.
      It seems like there is any change come between these versions that broke that contenxt menu.
      I also tested 1.598 and the problem exists also in that version of Jenkins

        Attachments

          Issue Links

            Activity

            Hide
            slide_o_mix Alex Earl added a comment -

            While having a workaround is good, this issue should be resolved so that the intended behavior works.

            Show
            slide_o_mix Alex Earl added a comment - While having a workaround is good, this issue should be resolved so that the intended behavior works.
            Hide
            nicolas_lacombe Nicolas Lacombe added a comment -

            Actually, the files proposed for deletion do exist, sorry about that.... but anyway deleting them does not solve the isse. Yes, using windows scheduler seems like a decent work-around, but nevertheless the issue should be logged somewhere, or fixed...

            Show
            nicolas_lacombe Nicolas Lacombe added a comment - Actually, the files proposed for deletion do exist, sorry about that.... but anyway deleting them does not solve the isse. Yes, using windows scheduler seems like a decent work-around, but nevertheless the issue should be logged somewhere, or fixed...
            Hide
            danielbeck Daniel Beck added a comment -

            The reason I asked for a new issue was that we hopefully get something actionable, a 1.5 year old issue with 40+ comments just isn't. There may be multiple issues here.

            Unsubscribing.

            Show
            danielbeck Daniel Beck added a comment - The reason I asked for a new issue was that we hopefully get something actionable, a 1.5 year old issue with 40+ comments just isn't. There may be multiple issues here. Unsubscribing.
            Hide
            remkop Remko Petersq added a comment -

            Same issue: i will open a new issue if that helps.

            Show
            remkop Remko Petersq added a comment - Same issue: i will open a new issue if that helps.
            Hide
            nullifiednll Donald Horn added a comment -

            I have the same issue with the latest version of Jenkins, this took a while to figure out for me, but I found a work around. 

            you'll need the Jenkins Slave Configuration XML and the Agent.jar file from your Jenkins webserver, as well as the secret keys. 

             

            1. Logon to the server with the configured slave, and navigate to the Slave Directory.
            2. Back this directory up
            3. Copy the Agent.jar to the root of this directory. 
              1. this can be found by clicking the offline slave and looking at it's configuration, then you can just right click and download. 
            4. Edit the Jenkins-Slave.xml
              1. Edit the below line, note that %BASE%\Slave.jar should be changed to agent.jar, and the URL should match what the Jenkins Master node is looking for if you don't know this value click on the offline slave it'll display it. ( Jenkins is case sensitive ). make sure the secret key matches the master.  
              2. <arguments>-Xrs -jar "%BASE%\agent.jar" -jnlpUrl http://Jenkins:port/computer/Computername/slave-agent.jnlp -secret XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</arguments>
            5. Save Jenkins-Slave.xml
            6. Start the Jenkins service, it will take a couple mins to check in but should work.

            Please let me know if this helps. 

            Show
            nullifiednll Donald Horn added a comment - I have the same issue with the latest version of Jenkins, this took a while to figure out for me, but I found a work around.  you'll need the Jenkins Slave Configuration XML and the Agent.jar file from your Jenkins webserver, as well as the secret keys.    Logon to the server with the configured slave, and navigate to the Slave Directory. Back this directory up Copy the Agent.jar to the root of this directory.  this can be found by clicking the offline slave and looking at it's configuration, then you can just right click and download.  Edit the Jenkins-Slave.xml Edit the below line, note that %BASE%\Slave.jar should be changed to agent.jar, and the URL should match what the Jenkins Master node is looking for if you don't know this value click on the offline slave it'll display it. ( Jenkins is case sensitive ). make sure the secret key matches the master.   <arguments>-Xrs -jar "%BASE%\agent.jar" -jnlpUrl http://Jenkins:port/computer/Computername/slave-agent.jnlp -secret XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</arguments> Save Jenkins-Slave.xml Start the Jenkins service, it will take a couple mins to check in but should work. Please let me know if this helps. 

              People

              • Assignee:
                Unassigned
                Reporter:
                chbiel Christopher Biel
              • Votes:
                6 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated: