- A plugin release has been announced (“plugin X version y.z”) but it is not available in the Update Center. This applies to already installed plugins in your instance as well as new ones (a fresh plugin installation) to install into a specific version.
- CloudBees Jenkins Enterprise (CJE)
- CloudBees Jenkins Operations Center (CJOC)
The following points need to be checked in order to identify the cause for the issue:
1. A new plugin releases should be published on the official sites:
- For OSS plugins, please check on the Jenkins IO Wiki plugin page. Note: It has been reported cases where a new release tag has been found on the respective SCM (mainly, Github) but it has not been available from the wiki page. In other words, that release seems to be tagged but it has not been published for some reason.
- For CB plugins, please check on the Cloudbees Product Release Notes.
Note: Check the
2. The plugin releases version should be available from your specific Update Center Service according to your core and product:
- For Jenkins: http://updates.jenkins-ci.org/update-center.json. It always points to the latest Jenkins version.
- For CJE:
- For CJOC:
- For CJE (under CAP):
- For CJOC (under CAP):
- Check if the information provided on the official sites taken in step 1 matches with the metadata on the JSON service (
- 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.
$CJOC_VERSIONunder CAP, differences on fixed and rolling are identified on the respective versions. Since Jenkins
2.7.19and onwards new coordinates are added, referring x to rolling (i.e.
2.7.19.x) vs 0.x to fixed (i.e.
3. Just for CJE or CJOC from 2.x, check if your instance is enrolled or not in the CloudBees Assurance Program (CAP).
Scenario description: CJE 220.127.116.11-rolling instance needs EC2 plugin to be updated from
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:
So, at this point, we can tell regarding the EC2 plugin (id:
- latest release is
- 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:
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.
"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=18.104.22.168.
For improving visualization, we move the analyzed EC2 metadata towards a JSON editor
So, the latest plugin release available on the Plugin Manager according to the core is
22.214.171.124 rolling is
3. Finally, it is time to check if the Beekeeper Upgrade Assistant is activated. Going to
$JenkinsURL/beekeeper/ we noticed that is enabled.
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.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 126.96.36.199-rolling under CAP.