instruction: Show me how to configure jenkins for CI/CD automation
output: If the list of available plugins is empty, the controller may be incorrectly
  configured or has not yet downloaded plugin meta-data from the Update Center.
  Clicking the Check now button forces Jenkins to attempt to contact its
  configured Update Center.
  
  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.
  
  The names of the plugin directories in the Update Site [ 1 ] are
  not always the same as the plugin’s display name. Searching plugins.jenkins.io for the desired plugin will provide the appropriate link to the archive file.
  
  Jenkins . instance . pluginManager . plugins . each { println ( "${it.getShortName()}: ${it.getVersion()}" ) }
  
  If a plugin file is removed but required by other plugins, the Jenkins
  controller may fail to boot correctly.
  
  The enable-plugin command was added to Jenkins in v2.136 .
  The disable-plugin command was added to Jenkins in v2.151 .
  java -jar jenkins-cli.jar -s http://localhost:8080/ enable-plugin PLUGIN ... [ -restart ]
  Enables one or more installed plugins transitively.
  
   PLUGIN : Enables the plugins with the given short names and their
   dependencies.
   -restart : Restart Jenkins after enabling plugins.
  java -jar jenkins-cli.jar -s http://localhost:8080/ disable-plugin PLUGIN ... [ -quiet ( -q )] [ -restart ( -r )] [ -strategy ( -s ) strategy]
  Disable one or more installed plugins.
  Disable the plugins with the given short names. You can define how to proceed with the
  dependant plugins and if a restart after should be done. You can also set the quiet mode
  to avoid extra info in the console.
  
   PLUGIN : Plugins to be disabled.
   -quiet (-q) : Be quiet, print only the error messages
   -restart (-r) : Restart Jenkins after disabling plugins.
   -strategy (-s) strategy : How to process the dependant plugins.
   - none: if a mandatory dependant plugin exists and
   it is enabled, the plugin cannot be disabled
   (default value).
   - mandatory: all mandatory dependant plugins are
   also disabled, optional dependant plugins remain
   enabled.
   - all: all dependant plugins are also disabled, no
   matter if its dependency is optional or mandatory.
  In the same way than enabling and disabling plugins from the UI requires a restart
  to complete the process, the changes made with the CLI commands will take effect
  once Jenkins is restarted. The -restart option forces a safe restart of the
  controller once the command has successfully finished, so the changes will be
  immediately applied.
  Pinned plugins feature was removed in Jenkins 2.0. Versions later than Jenkins
  2.0 do not bundle plugins, instead providing a wizard to install the most
  useful plugins.
  
  The score value is always based on the latest available data.
  This means that there is no score of a specific release of a plugin.
  What is available on the installed and updates page of the plugin manager does not stand for the version already installed.