A plugin release is not available from Update Center


  • A plugin release has been announced (“plugin X version y.z”) but it is not available in the Update Center in my instance.


IMPORTANT : In case a certain plugin is not available via Update Center, do not install/upgrade via Advanced Tab > Upload plugin without CloudBees’ agreement. Manual Upload could break your instance because of dependency mismatches among other plugins and/or core incompatibility.

The following points need to be checked in order to identify the root cause. They are valid for installed/existing plugins in your instance as well as new ones (a fresh plugin installation).

1. Check first if your instance is connected to a Custom Update Center (UC) from a Operation Center. If so, “plugin X version y.z” needs to be promoted in order Client/Managed Master can install it. In the case that it has been promoted but it is still not available, please click on Check Now on the Advance Properties tab in the Plugin Manager to force an update.

2. A new plugin releases should be published on the official sites:

Note: Check the id, version and requiredCore attributes.

3. There are plugins that cannot be installed in any of their versions because they have been blacklisted by jenkins.io.

4. Just for CloudBees Jenkins since 2.x, check if your instance is enrolled or not in the CloudBees Assurance Program (CAP). Please see Plugins missing from Update Center after installing CloudBees Jenkins v2.x

5. The plugin releases version should be available from your specific Update Center Service according to your core, product and enrolment into the CloudBees Assurance Program (CAP)

  • For OSS Update Center: http://updates.jenkins-ci.org/update-center.json. It always points to the latest Jenkins version.

  • For CloudBees’s Update Center, depending on the product:

    • A. 1CloudBees Jenkins Enterprise - Managed Master

      • A.1 CAP: http://jenkins-updates.cloudbees.com/update-center/envelope-cje-mm/update-center.json?id=cap-cje-mm&version=<VERSION>
      • A.2 No CAP: http://jenkins-updates.cloudbees.com/update-center/cje-mm/update-center.json?id=cje-mm&version=<VERSION>
    • B. CloudBees Jenkins Enterprise - Operations Center

      • B.1 CAP: http://jenkins-updates.cloudbees.com/update-center/envelope-cje-oc/update-center.json?id=cap-cje-oc&version=<VERSION>
      • B.2 No CAP: http://jenkins-updates.cloudbees.com/update-center/cje-oc/update-center.json?id=cje-oc&version=<VERSION>
    • C. CloudBees Jenkins Team

      • C.1 CAP: http://jenkins-updates.cloudbees.com/update-center/envelope-cjt/update-center.json?id=cap-cjt&version=<VERSION>
      • C.2 No CAP: http://jenkins-updates.cloudbees.com/update-center/cjt/update-center.json?id=cjt&version=<VERSION>
    • D. CloudBees Jenkins Platform - Client Master

      • D.1 CAP: http://jenkins-updates.cloudbees.com/update-center/envelope-cje/update-center.json?version=<VERSION>
      • D.2 No CAP: http://jenkins-updates.cloudbees.com/update-center.json?id=jenkins-enterprise&version=<VERSION>
    • E. CloudBees Jenkins Platform - Operations Center

      • E.1 CAP: http://jenkins-updates.cloudbees.com/update-center/envelope-cjoc/update-center.json?version=<VERSION>
      • E.2 No CAP: http://jenkins-updates.cloudbees.com/update-center/operations-center/update-center.json?id=jenkins-operations-center&version=<VERSION>


  1. Check if the information provided on the official sites taken in step 1 matches with the metadata on the JSON service (id, version and requiredCore).
  2. A new release of a OSS plugin could not be available in CloudBees Update Centers, if it is not available on the Jenkins Update Center at first.
  3. Differences on fixed and rolling are identified on the respective versions. Since Jenkins 2.7.19 and onwards new coordinates are added, referring x to rolling (i.e. 2.7.19.x) vs 0.x to fixed (i.e.

Example Scenario

Scenario description: CJE instance needs EC2 plugin to be updated from 1.35 to 1.36 but in the Plugin Manager does not offer the option:



1. At the moment of writing this article, the wiki page of the EC2 plugin looked like:

ec2 on wiki page

So, at this point, we can tell regarding the EC2 plugin (id: ec2) that:

  • latest release is 1.36
  • required core is 1.651.3. So this requirement is met because the example scenario is on

As it is an OSS plugin, GitHub repo of the plugin also can be checked:

ec2 on github

Seeing this matching (wiki-GitHub), it can be told that latest release of the plugin has been done successfully and it is available on Jenkins Update Center.

2. Then, "ec2" (plugin id) is used for searching the plugin metadata on the service http://jenkins-updates.cloudbees.com/update-center/envelope-cje/update-center.json?version=

ec2 on the Service

For improving visualization, we move the analyzed EC2 metadata towards a JSON editor

ec2 on the Service

So, the latest plugin release available on the Plugin Manager according to the core is rolling is 1.35

3. Finally, it is time to check if the Beekeeper Upgrade Assistant is activated. Going to $JenkinsURL/beekeeper/ we noticed that is enabled.


If this is a newer instance you will need to do one more step to see if it is enabled where you go to the beekeeper link:


Then click the sidebar link called CAP Configuration where you will find the same UI again:


So, without restarting the instance, we disabled it (do not forget to click on Save)…


… and that moment, the Update Center endpoint changes from http://jenkins-updates.cloudbees.com/update-center/envelope-cje/update-center.json to http://jenkins-updates.cloudbees.com/update-center.json, it gets outside the “envelope”.

And without being enrolled in the CloudBees Assurance Program, latest released of the plugin is available under the Updates tab so.. for this specific scenario the root cause was found: ec2 is not available yet for CJE under CAP.


Have more questions?


  • 0
    Parag Doke


    1. How to identify version of the Jenkins instance I am running ? If it is a docker container invoked via docker run -d cloudbees/jenkins-enterprise, does it mean I am running "CloudBees Jenkins Enterprise - Managed Master" ? If I follow the instructions to configure a yum repo and install Jenkins Enterprise using yum, does it mean I am running "CloudBees Jenkins Platform - Client Master" ? And that is not Enterprise ? But neither OSS ? The nomenclature is very confusing :-(
    2. Does the version value (from "version=<VERSION>") need to have "-rolling" text too ?
    3. At the file system level, how does one check if the right json was picked up ? For example, on a docker container (instance of cloudbees/jenkins-enterprise image), under /var/jenkins_home/updates folder, there are 3 json files: cap-cje.json, cje-offline.json and jenkins-enterprise.json. Which file should one compare with what those URLs return ?
Please sign in to leave a comment.