Using CloudBees plugins with Jenkins

Last modified by Harpreet Singh on 2013/04/08 22:33

Deprecated - Jenkins Enterprise by CloudBees plugin is the preferred way to do upgrade Jenkins OSS instances to have CloudBees plugins.

As of Nectar 11.10 and Jenkins 1.437, you can now run CloudBees value-add plugins on stock Jenkins (this is because Nectar 11.10 itself is basically stock Jenkins + a bunch of value-add plugins.) This is primarily intended for those customers who would like to update more frequently (than Nectar's 6 month release cycle), or those who has locally modified Jenkins.

This same same workflow allows you to evaluate those plugins with your Jenkins instances before purchasing a license.


  1. Run this Groovy script from Jenkins Groovy script console to register CloudBees plugin update center to your Jenkins and install necessary certificate. This script will report "success" at the end if it works correctly. 
  2. Go to plugin update center, and you'll now see a bunch of CloudBees plugins, such as "cloudbees-folder" for the folder feature, "cloudbees-template" for the template feature. You can install them like you install any other plugins.
  3. Once you install any of the value-add plugin and restart Jenkins, you'll be prompted to register your Jenkins with a proper Nectar license. If you are already a customer, you enter the license here. If you are evaluating those plugins, obtain the evaluation license by filling in your contact information.

Uninstalling proprietary plugins

If you evaluate our value-add plugins in this manner and decide not to purchase a license, you need to remove all the value-add plugins to keep using it as a stock Jenkins installation. In particular, please remove the "cloudbees-license" plugin, and all the other plugins will cease to function, and your Jenkins should boot up normally without any of the value-add features.

Created by Harpreet Singh on 2012/02/11 02:22