Managing plugins

Plugins can be installed, updated, and disabled on CloudBees Core, CloudBees Jenkins Distribution, CloudBees Jenkins Platform, and CloudBees Jenkins Enterprise 1.x.

If using CloudBees Core masters, these actions can be performed both from Operations Center and from the command line.

If you are testing functionality known to require plugin versions newer than those currently identified as verified or trusted, you can disable the Beekeeper Upgrade Utility for the duration of your tests.
This chapter describes how to manage plugins from Operations Center and Client Masters. To manage plugins from the command line, refer to Managing plugins from the command line.

Installing a plugin from Operations Center

Installing an Operations Center plugin is performed through the Manage Plugins page.

To install an Operations Center plugin:

  1. Access the Manage Jenkins area.

  2. On the Manage Jenkins page, scroll down and click Manage Plugins.

  3. On the resulting Plugin Manager page, check that the plugin is not already installed by clicking the Installed tab and begin typing the name of the Operations Center plugin to install into the top-right Filter field.

    If the page’s list shows the plugin, then it is already installed on Operations Center and you need not proceed any further. However, ensure the plugin’s Enabled check box is selected.

    If the plugin does not appear in the list, then it is not installed. Therefore, continue on.

  4. Click the Available tab and begin typing the name of the Operations Center plugin to install into the top-right Filter field.

  5. In the page’s list, select the plugin’s Install check box on the left.

  6. Scroll down the page and click either the Install without restart or Download now and install after restart button.

Updating a plugin from Operations Center

Updating an Operations Center plugin is also performed through the Manage Plugins page.

To update an Operations Center plugin:

  1. Access the Manage Jenkins area.

  2. On the Manage Jenkins page, scroll down and click Manage Plugins.

  3. On the resulting Plugin Manager page, check that plugin updates are available by ensuring the Update tab is selected and clicking the Check now button towards the end of the page.

    If the page’s list does not show any plugins, then no plugin updates are available. There is no need (and you cannot) proceed any further.

    If a plugin does appear in the list, then an updated version of the plugin is available. To update the plugin, continue on.

  4. In the page’s list, select the plugin’s Install check box on the left.

  5. Scroll down the page and click the Download now and install after restart button.

Installing a plugin from Client Master

Installing a Client Master plugin is performed through the Manage Plugins page.

To install a Client Master plugin:

  1. Access the Manage Jenkins area of the appropriate Client Master.

  2. On the Manage Jenkins page, scroll down and click Manage Plugins.

  3. On the resulting Plugin Manager page, check that the plugin is not already installed by clicking the Installed tab and begin typing the name of the Client Master plugin to install into the top-right Filter field.

    If the page’s list shows the plugin, then it is already installed on Client Master and you need not proceed any further. However, ensure the plugin’s Enabled check box is selected.

    If the plugin does not appear in the list, then it is not installed. Therefore, continue on.

  4. Click the Available tab and begin typing the name of the Client Master plugin to install into the top-right Filter field.

  5. In the page’s list, select the plugin’s Install check box on the left.

  6. Scroll down the page and click either the Install without restart or Download now and install after restart button.

Updating a plugin from Client Master

Updating a Client Master plugin is also performed through the Manage Plugins page.

To update a Client Master plugin:

  1. Access the Manage Jenkins area of the appropriate Client Master.

  2. On the Manage Jenkins page, scroll down and click Manage Plugins.

  3. On the resulting Plugin Manager page, check that plugin updates are available by ensuring the Update tab is selected and clicking the Check now button towards the end of the page.

    If the page’s list does not show any plugins, then no plugin updates are available. There is no need (and you cannot) proceed any further.

    If a plugin does appear in the list, then an updated version of the plugin is available. To update the plugin, continue on.

  4. In the page’s list, select the plugin’s Install check box on the left.

  5. Scroll down the page and click the Download now and install after restart button.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.