In our corporate environment, we have a custom update center that contains a small set of blessed plugins whose versions we want to enforce. This update center serves as the primary. In addition, we want to make use of the JenkinsCI update center as the secondary to allow users to install optional plugins that are not part of the blessed corporate plugin baseline.

We have updated our hudson.model.UpdateCenter.xml to contain:

<?xml version='1.0' encoding='UTF-8'?>
<sites>
  <site>
    <id>default</id>
    <url>https://update-center.company.com/update-center.json</url>
  </site>
  <site>
    <id>jenkinsci-stable</id>
    <url>http://updates.jenkins-ci.org/stable/update-center.json</url>
  </site>
</sites> 

When attempting to install a new plugin that is only located in jenkinsci-stable using the above configuration, the following error is seen:

No such plugin: timestamper.default

The reason for this is due to the fact that id that is used to identify the plugin is the id from the update-center.json itself rather than the id from the config file hudson.model.UpdateCenter.xml