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

Installing a new plugin jpi file via CLI does not really install without restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • cli, plugin-proposals
    • None
    • Jenkins 1.455, on RHEL with Winstone.

      I issued a install plugin command to install a plugin .jpi file on my local box using Jenkins CLI onto the Jenkins instance in the Data Center.

      The command returned 0 (success) but it only copied the .jpi plugin file in the ${JENKINS_HOME}/plugins directory. I am thinking that it should copy, and install it right away without restart.

      Command issue:
      bash-3.2$ ./install-plugin1.sh sjc-bld120-lnx timestamper.jpi
      jenkins = sjc-bld120-lnx
      login to sjc-bld120-lnx ...
      installing timestamper.jpi to sjc-bld120-lnx ...
      Installing a plugin from local file: /Users/ingunawa/Data/Jenkins/plugins/timestamper.jpi
      bash-3.2$ echo $?
      0

      the bash script simply login me with my credential and install-plugin; I am administrator of the Jenkins:

      java -jar /Users/ingunawa/Data/Jenkins/jenkins-cli.jar -s http://$n:8080 login --username ingunawa --password-file cec-password.txt

      java -jar /Users/ingunawa/Data/Jenkins/jenkins-cli.jar -s http://$n:8080 install-plugin /Users/ingunawa/Data/Jenkins/plugins/$PLUGIN;

      jenkins.log:
      Jan 30, 2013 4:49:15 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
      INFO: Accepted connection #6 from /10.21.69.43:64363
      Jan 30, 2013 4:49:25 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
      INFO: Accepted connection #7 from /10.21.69.43:64398

      -Indra

          [JENKINS-16562] Installing a new plugin jpi file via CLI does not really install without restart

          evernat added a comment - - edited

          Historically, the plugins update center installs a plugin, only after a restart.
          So I do not think that this issue is a defect, but it describes a "standard" behaviour of Jenkins.

          You could instead update your issue to suggest that a new CLI command is created, in order to be able to install a plugin without restart (if this feature was not yet added since your issue, of course).
          Given the case, you can submit a pull request to implement the feature.

          evernat added a comment - - edited Historically, the plugins update center installs a plugin, only after a restart. So I do not think that this issue is a defect, but it describes a "standard" behaviour of Jenkins. You could instead update your issue to suggest that a new CLI command is created, in order to be able to install a plugin without restart (if this feature was not yet added since your issue, of course). Given the case, you can submit a pull request to implement the feature.

          Oleg Nenashev added a comment -

          No response from the requester/no votes => closing as "not a defect"

          Oleg Nenashev added a comment - No response from the requester/no votes => closing as "not a defect"

            Unassigned Unassigned
            ingunawa Indra Gunawan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: