CloudBees Free Enterprise Plugins

This plugin removes any update center definitions added by previous versions of this plugin

Uninstallation

Uninstallation

To uninstall, simply disable or delete the CloudBees Free Enterprise Plugins plugin and an any of the proprietary plugins that you want. If you disable only the CloudBees Free Enterprise Plugins you will no longer be able to access the CloudBees proprietary update center. If you disable or delete only the CloudBees proprietary plugins, they will not be reinstalled unless you upgrade the CloudBees Free Enterprise Plugins plugin to a newer version.

Version History

Version 6.0 (Dec 14, 2015)

• Tombstone release. This version will remove the update center definitions. NOTE: Prior to upgrade ensure that you have upgraded the free-license-plugin to version 7.0 as that version removes the requirement for a license on the closed source free plugins.

Version 4.2 (Sep 2, 2013)

• Upgrade required Jenkins core to 1.480.3
• Upgrade minimum version of installed plugins to latest releases.

Version 4.1 (Jul 30, 2013)

• Upgrade required Jenkins core to 1.466
• Use ACL.impersonate to avoid a race condition when elevating privileges.
• Use a lock on UpdateCenter to ensure changes are atomic.

Version 4.0 (Apr 10, 2013)

• Update to version 4.0 of the cloudbees-license plugin to resolve classloading conflicts with bouncycastle

Version 1.11 (Mar 14, 2013)

• Upgrade required core to 1.447 as this is the minimum required for the current versions of the free plugins
• Upgrade async-http-client dependency to 1.7.8
• Upgrade credentials dependency to 1.3.1
• Ensure the cloudbees-credentials plugin does not get disabled (while the free plugins are installed) as this breaks the free plugins
• Ensure the cloudbees-registration plugin does not get disabled (while the free plugins are installed) as this breaks the free plugins
• Upgrade the cloudbees-license plugin to latest
• Upgrade the free-license plugin to latest
• Upgrade the nectar-license plugin to latest so that Jenkins Enterprise in-place upgrades work.
• Upgrade the cloudbees-folder plugin to latest
• Upgrade the cloudbees-wasted-minutes-tracker to latest
• Upgrade the cloudbees-deployer-plugin to latest
• Fix plugin to work around breaking API change in Jenkins core
• If the safe restart is cancelled by the user, don't display the banner

Version 1.10 (Jul 18, 2012)

• Upgrade to Folders version 3.2 to pick up the ability to move items between folders

• Upgrade to CloudBees Deployer version 3.7.8 to pick up a fix for the 'Deploy Now' functionality when the master does not have any executors and correspondingly does not have a Maven Home which was giving a NPE with the token expansion functionality for Maven2 project type based 'Deploy Now' deployments

Version 1.9 (Jul 16, 2012)

• Fix registration on Jenkins 1.474 or newer.

Version 1.8 (Jul 9, 2012)

• Rebranded from "CloudBees Plugin Gateway plugin" to "CloudBees Free Enterprise Plugins"

• Updated base versions of the Free Enterprise plugins to pull in the latest fixes for people installing initially.

Version 1.7 (Jun 1, 2012)

• Some authentication plugins do not propagate ACL.SYSTEM correctly to system threads, so this now assigns ACL.SYSTEM for the installer thread while installing the CloudBees plugins.

Version 1.6 (Jun 1, 2012)

• Added some diagnostics when plugin installation fails
• Only display the progress of CloudBees plugin installation to administrators

Version 1.5 (May 15, 2012)

• Update the required minimum version of the CloudBees Deployer Plugin

Version 1.4 (May 15, 2012)

• Fix installation when Jenkins is running on JBoss as a Servlet container.

Version 1.3 (May 11, 2012)

• Updated core plugin versions.

Version 1.2 (Apr 27, 2012)

• Fixes issue with installing the plugin when Jenkins is not on the ROOT context path.

If you are stuck with version 1.1 installed and your Jenkins installation is not on the ROOT context path, here is the procedure to follow to get your system upgraded:

1. 1. First you need to disable all the plugins that require the cloudbees-license. When the registration screen is active visit the following URL:

      http://jenkins-hostname:port/context-path/disable?plugin=cloudbees-license
      

      where you have replaced the _http://jenkins-hostname:port/context-path_ with the correct root URL for your Jenkins instance.
   2. Then restart Jenkins. It should start up with some of the cloudbees plugins that do not require a license installed.
   3. Clear your browser cache. It cannot be stated how important this step is.
   4. Go to the Manage Jenkins | Manage Plugins | Advanced tab and select the "Check now" option.
   5. Go to the Manage Jenkins | Manage Plugins | Updates tab and select the "CloudBees Plugin Gateway Plugin" ensuring that you are selecting version 1.2. Select the option to restart after the plugin is installed.
   6. When Jenkins has restarted, the plugin will then proceed as before to download the newer plugins, and restart Jenkins again. At this point the registration screen should work.

• Note: The reasons for the rather complex procedure above are:
  • Jenkins only checks for update center metadata being changed once every 24 hours.
  • Jenkins downloads the update center metadata via the browser rather than trying to connect to the update center itself, the browser's cache can result in incorrect metadata being picked up.
  • When Jenkins installs a plugin it will install all of that plugin's dependencies even if it has just immediately prior installed the plugin's dependencies, thus our bootstrap of all the required plugins can be hindered.
• This above procedure is not required if you have Jenkins's servlet container using a ROOT context as you would have been able to register the system and receive a license already.  

Version 1.1 (Apr 17, 2012)

• Fixed issue with installing the CloudBees Deployer plugin.

Version 1.0 (Apr 17, 2012)

• Initial release version.