A plugin release is not available from Update Center

Article ID:230655088
3 minute readKnowledge base


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


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 an Operation Center. If so, "plugin X version y.z" needs to be promoted in order Client/Managed controller 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:

    • For Jenkins plugins, please check on the Jenkins plugin page.

      It has been reported cases that release seems to be tagged, but it has not been published for some reason.
    • For CloudBees plugins, please check on the CloudBees CI Plugins index.

      Check the id, version and requiredCore attributes.
  3. There are plugins that cannot be installed in any of their versions because they have been block-listed by jenkins.io.

  4. Check if your instance is enrolled or not in the CloudBees Assurance Program (CAP). If it is on and you need to install a newer version than recommended, please use Beekeeper plugin exceptions.

  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 Jenkins Update Center: https://updates.jenkins-ci.org/update-center.json. It always points to the latest Jenkins version.

    • For CloudBees CI on modern cloud platforms:

      • Operations center

        • CAP: https://jenkins-updates.cloudbees.com/update-center/envelope-core-oc/update-center.json?id=cap-core-oc&version=<VERSION>

        • No CAP: https://jenkins-updates.cloudbees.com/update-center/core-oc/update-center.json?id=core-oc&version=<VERSION>

      • Managed controller

        • CAP: https://jenkins-updates.cloudbees.com/update-center/envelope-core-mm/update-center.json?id=cap-core-mm&version=<VERSION>

        • No CAP: https://jenkins-updates.cloudbees.com/update-center/core-mm/update-center.json?id=core-mm&version=<VERSION>

    • For CloudBees CI on traditional platforms

      • Operations center

        • CAP: https://jenkins-updates.cloudbees.com/update-center/envelope-core-oc-traditional/update-center.json?id=cap-core-oc-traditional&version=<VERSION>

        • No CAP: https://jenkins-updates.cloudbees.com/update-center/core-oc-traditional/update-center.json?id=core-oc-traditional&version=<VERSION>

      • Client controller

        • CAP: https://jenkins-updates.cloudbees.com/update-center/envelope-core-cm/update-center.json?id=cap-core-cm&version=<VERSION>

        • No CAP: https://jenkins-updates.cloudbees.com/update-center/core-cm/update-center.json?id=core-cm&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 an Jenkins plugin could not be available in CloudBees Update Centers, if it is not available on the Jenkins Update Center at first.

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 https://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)…​

  1. and that moment, the Update Center endpoint changes from https://jenkins-updates.cloudbees.com/update-center/envelope-cje/update-center.json to https://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.