Child pages
  • UpdateSites Manager plugin
Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID



In Latest Release
Since Latest Release

Latest Release
Latest Release Date
Required Core

2.0.0 (archives)
Feb 28, 2016

Source Code
Issue Tracking
Pull Requests

Open Issues
Pull Requests
IKEDA Yasuyuki (id: ikedam)



2016-Oct 616
2016-Nov 624
2016-Dec 620
2017-Jan 655
2017-Feb 678
2017-Mar 682
2017-Apr 715
2017-May 755
2017-Jun 749
2017-Jul 724
2017-Aug 771
2017-Sep 774

This plugin is to manage update sites, where Jenkins accesses in order to retrieve plugins.

What's this?

Sites where Jenkins finds and downloads new plugins, which are called update sites, are listed in hudson.model.UpdateCenter.xml.
This plugin enables you to manage update sites in the Jenkins configuration page with web browsers.
Following features are available:

  • "Manage UpdateSites" link is added to "Manage Jenkins" page.
  • You can list, add, edit, or delete an update site registered with Jenkins.
  • When adding a new update site, you specify following fields:
    • Disable this site
      • Check if you want to disable the update site temporary.
    • ID
      • The ID of the update site. Value to specify here is specified by the update site.
    • URL
      • The URL of the update site. Usually, the URL to update-center.json.
    • Note
      • A note. It is not used by Jenkins, and you can note anything here.
    • CA Certificate
      • CA Certificate for this site. This is useful for a update site which is signed with a self-signed certificate.


  • "Manage UpdateSites" is added in "Manage Jenkins" page.
  • You can list, add, edit, or delete an update site registered with Jenkins.
    • You can easily register an update site using a self-signed certificate by specifying CA cetificate for that site.


  • Following update sites are listed in "Manage UpdateSites" page, but cannot be edited nor deleted.
    • Default update site (its ID is "default"). This can be configured in "Manage Plugins" page.
    • Update sites provided by other plugins. These plugins must provide their own configuration pages for their update sites.


  • Create a menu icon.

How do I create a update center?



To report a bug or request an enhancement to this plugin please create a ticket in JIRA (you need to login or to sign up for an account). Also have a look on How to report an issue

Key T P Summary

Change Log

Version 2.0.0 (Feb 28, 2016)

  • Now targets Jenkins >= 1.609
  • Supports server-based download (JENKINS-32376)
    • server-based download was introduced in Jenkins 1.557 and enabled by default in Jenkins 1.600.
  • Changed the design of the configuration page (See the above screenshot)
    • You can list and edit update sites in the same page.
  • Refactored the code and doesn't preserve binary compatibilities with versions < 2.0.0.
    • Preserves configuration compatibilities and doesn't affect users in almost all cases.
    • Plugins depending on update-sites-manager might not work when you upgrade from versions < 2.0.0.
    • No official plugins provided by Jenkins communities doesn't depend on update-sites-manager for now.
    • Private plugins (e.g. plugins developed internally in your company) might be broken.
      • Please let me know if features you need for those plugins is no longer available.

Version 1.0.1 (Jul 28, 2013)

  • Added help texts.

Version 1.0.0 (Apr 09, 2013)

  • Initial release.


  1. Unknown User (jl.pinardon)


    I have create a brand new Jenkins instance and the very last update site manager plugin.
    I want to "connect" the instance to only a custom update center. In other words, I don't want to be linked with the jenkins one.
    I found no way to do that.
    If I only configure the plugin to connect to the in house UC, it works. But if I remove also the jenkins update center, the "check now" fails with a java exception :

    Malformed URL Java Exception
    Stack trace no protocol: ?id=default&version=2.7.2
    	at<init>(Unknown Source)
    	at<init>(Unknown Source)
    	at<init>(Unknown Source)
    	at hudson.model.UpdateSite.updateDirectlyNow(
    	at hudson.PluginManager.doCheckUpdatesServer(
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    	at java.util.concurrent.ThreadPoolExecutor$ Source)
    	at Source)

    This occurs with both an instance on a windows machine or a linux one. In both tests, the java version was
    And the same behavior is observed with the very last LTS version or an older 2.16.

    1. Unknown User (jl.pinardon)

      Please, note that the inhouse UC is an update center job on a jenkins instance.

  2. Unknown User (jl.pinardon)

    It is really strange, because it appears that though this message is displayed, the plugins list is actually updated !
    So, what does this message means ?

Write a comment…