Using the Jenkins CLI Advanced installation From the web UI Administrators may also use the Jenkins CLI which provides a command to install plugins. Scripts to manage Jenkins environments, or configuration management code, may need to install plugins without direct user interaction in the web UI. The Jenkins CLI allows a command line user or automation tool to download a plugin and its dependencies. The Update Center only allows the installation of the most recently released version of a plugin. In cases where an older release of the plugin is desired, a Jenkins administrator can download an older  .hpi  archive and manually install that on the Jenkins master. Assuming a  .hpi  file has been downloaded, a logged-in Jenkins administrator may upload the file from within the web UI: 1. Navigate to the  Manage Jenkins  >  Manage Plugins  page in the web UI. 2. Click on the  Advanced  tab. 3. Choose the  .hpi  file under the  Upload Plugin  section. 4. Upload  the plugin file. 161 java -jar jenkins-cli.jar -s http://localhost:8080/ install-plugin SOURCE ... [- deploy] [-name VAL] [-restart] Installs a plugin either from a file, an URL, or from update center.  SOURCE : If this points to a local file, that file will be installed. If this is an URL, Jenkins downloads the URL and installs that as a plugin.Otherwise the name is assumed to be the short name of the plugin in the existing update center (like "findbugs"),and the plugin will be installed from the update center.  -deploy : Deploy plugins right away without postponing them until the reboot.  -name VAL : If specified, the plugin will be installed as this short name (whereas normally the name is inferred from the source name automatically).  -restart : Restart Jenkins upon successful installation.