About Plugins

4 minute read

CloudBees CI and CloudBees Jenkins Platform include access to the CloudBees Assurance Program, which is enabled by default through the Beekeeper Upgrade Utility ("Beekeeper"). By monitoring plugin versions and comparing the configuration of your instance to plugins identified by CloudBees as verified, trusted, or unverified, Beekeeper provides "envelope enforcement" to provide stability and security.

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.

If you’re running CloudBees CI in a secured environment, refer to Managing plugins in a secured environment. Otherwise, refer to the plugin management documentation to learn how to install and manage plugins from the UI and the command line.

Through the CloudBees Assurance Program, CloudBees classifies plugins into tiers according to how much risk to a given installation’s stability a given plugin may pose. See CloudBees plugin support policies for details.

Refer to the release notes for each product for the full list of plugins included in specific products and specific product versions as well as what support tier they are in:

This page highlights a few of these plugins.

Large installation plugins

These plugins help administrators manage large numbers of jobs, projects, and teams.

Optimized utilization plugins

CloudBees CI helps administrators make better use of existing resources with the following plugins:

Security plugins

CloudBees CI helps administrators secure their projects and their installations with the following plugins:

Cloud native plugins

Use these plugins with their respective cloud providers.

Manage builds plugins

These plugins help you manage your builds.

  • Restart Aborted Builds plugin

    Save at least a partial record of every build immediately after it starts and after every configured build step

  • Consolidated Build View plugin

    See which builds were run for what reason, and immediately jump to the console log for each

  • GitHub Branch Source plugin

    Create a new project based on the repository structure from one or more GitHub users or organizations using Pipeline scripts in the repo

  • Nodes Plus plugin

    Gain additional functionality for managing build nodes, including the ability to assign owners to nodes who are notified when the node availability changes

  • Quiet Start plugin

    Restart in "quieting down" state so that scheduled jobs don’t restart, useful for maintenance

  • SSH Build Agents plugin

    Use an alternative SSH agent connector that uses a Non-Blocking I/O architecture

  • Template plugin

    Provide users a simplified and directed experience for configuring jobs by only allowing users to define a few parameters to enforce consistency, best practices, and enterprise rules without overhead

  • Validated Merge plugin

    Enable a suite of plugins which supports implementing and integrating continuous delivery pipelines into Jenkins as code

Docker plugins

These plugin help you manage your Docker images and containers.

CloudBees support plugins

These plugins allow CloudBees to provide support.

  • CloudBees Assurance Program plugin

    Automatically monitor and optionally modify plugins for compatibility

  • Jenkins Health Advisor by CloudBees

    Upload a support bundle to CloudBees and receive advise about potential issues and recommendations based on the knowledge of CloudBees experts

  • Support plugin

    Generate a bundle of all the commonly requested information used by CloudBees when resolving support issues, also available for download and installation into any Jenkins installation

  • User Activity Monitoring plugin

    Count and monitor user licenses with User Activity Monitoring

Distributed workload plugins

Some recommendations for plugins related to distributed workload: