The CloudBees Assurance Program specifies the set of plugins, plugin versions, and plugin dependencies that are either verified or trusted, depending on how much they have been tested. This provides greater stability and security for Jenkins environments. Not only are these plugins independently stable, but they are tested as a whole (in aggregate) to ensure compatibility with each other and the Jenkins instance.
The primary administrator interface for the CloudBees Assurance Program is the Beekeeper Upgrade Assistant. It provides a centralized view of the monitored Jenkins plugins, recommended actions, and configuration options. The Beekeeper Upgrade Assistant allows administrators to review and install upgrades for plugins. Additionally, administrators can enable automatic upgrades or downgrades of plugins which are not in compliance with the support policy for the CloudBees Assurance Program.
When enrolled in the CloudBees Assurance Program, two changes are immediately made to the instance: the Beekeeper Upgrade Assistant displays the current compliance status with CloudBees Assurance Program, and the Update Center configuration is modified to point at the CloudBees Assurance Program Update Center.
The CloudBees Assurance Program Update Center modifies the list of "Updates" and "Available" plugins on the Manage Plugins page to hide plugins that would be incompatible with CloudBees Assurance Program due to dependencies on plugin versions which are outside of the CloudBees Assurance Program.
The Beekeeper Upgrade Assistant regularly evaluates the state of the instance to ensure compliance with CloudBees Assurance Program and provides an "Administrative Monitor" to alert administrators to upgrades needing their attention.
When an upgrade is available, the administrator is notified by Beekeeper Upgrade Assistant, with a notification on the "Manage Jenkins" Page and on the administrative monitor shown in the header for other pages.
Clicking Manage will navigate to a Beekeeper Upgrade Assistant screen that outlines the available upgrades.
To reconcile the difference between revisions, Beekeeper Upgrade Assistant reports what actions it will need to perform to upgrade successfully (such as downgrading or upgrading installed plugins).
Before any upgrade, CloudBees recommends creating a backup of the instance in case there is some unexpected failure during the upgrade process.
The new product release notification shows the offered release and a More Info… button that directs the administrator to a page providing additional information about the upgrade.
The upgrade page shows:
Current version and the offered release
Link to Release Notes describing the new features, fixes and known issues
Results of a simulation of the upgrade (including changes in core and/or plugin versions)
Link to documentation and downloads
The CloudBees Assurance Program can also provide incremental upgrades. Incremental upgrades include a subset of functionality delivered prior to the full product release. For example, incremental upgrades may deliver plugin security fixes or important new features that can’t wait until the next full product release.
Incremental upgrades appear in the page with a message that a new revision is available. The upgrade page shows the current and offered revisions as well as a simulation of the changes.
Depending on the plugins you have installed, no change may be needed in the running instance. You should choose the upgrade even in those cases so that Beekeeper Upgrade Assistant uses the upgraded configuration.
Given that incremental upgrades are usually used for important inter-release upgrades of the recommended configuration, such as security upgrades, if you perform an initial installation of a version for which an incremental upgrade is available (and the instance is connected to CloudBees Update Center) you will have the option of applying the upgrade from the setup wizard:
If you decide to install the incremental upgrade at this point, depending on the affected plugins, an additional restart may be required at the end of the installation process. If you decide to skip the upgrade in the setup wizard, it will be offered by the Beekeeper Upgrade Assistant as described above so it can be installed at the most convenient time.
If for any reason you need to automatically skip this behavior,
just set the system property
Beekeeper Upgrade Assistant allows administrators to easily and automatically keep their verified plugins up-to-date with the versions recommended by the CloudBees Assurance Program. To enroll the instance in automatic CAP version compliance, check the Allow automatic upgrades of plugins on restart setting and click Save. It’s recommended that you restart the instance after making changes to allow Beekeeper Upgrade Assistant to perform any necessary automatic upgrades.
If Allow automatic upgrades of plugins on restart was not enabled, Beekeeper Upgrade Assistant will report when the instance is out of compliance with the verified plugins recommended by CAP. To resolve the drift out of compliance, the administrator may either manually follow the Beekeeper Upgrade Assistant recommended actions, or enable Allow automatic upgrades of plugins on restart and then restart the instance to allow the necessary upgrades to complete.
If an upgrade fails, Beekeeper Upgrade Assistant will notify the administrator and allow the upgrade to be canceled.
Beekeeper Upgrade Assistant supports automatic plugin upgrades and downgrades to provide comprehensive compliance with the CloudBees Assurance Program. By checking Allow automatic downgrades of plugins on restart, Beekeeper Upgrade Assistant automatically downgrades any installed plugins that exceed the versions explicitly recommended by CAP. While this behavior will only affect plugins considered verified and part of the CloudBees Assurance Program, it may have unintended side effects on stability if the instance has been taking advantage of features and configurations provided by more recent versions of those plugins.
Consequently, this option should be used sparingly.
Online version published by CloudBees, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
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 book, 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 book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.