|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
nickolay.rumyant...@emc.com (JIRA) Tue, 17 Jul 2012 05:06:22 -0700
- [JIRA] (JENKINS-14301) Failed to use mu... nickolay.rumyant...@emc.com (JIRA)
- [JIRA] (JENKINS-14301) Failed to u... nickolay.rumyant...@emc.com (JIRA)
- [JIRA] (JENKINS-14301) Failed to u... nickolay.rumyant...@emc.com (JIRA)
- [JIRA] (JENKINS-14301) Failed to u... nickolay.rumyant...@emc.com (JIRA)
- [JIRA] (JENKINS-14301) Failed to u... nickolay.rumyant...@emc.com (JIRA)
- [JIRA] (JENKINS-14301) Failed to u... nickolay.rumyant...@emc.com (JIRA)
I seek through code and found the reason of that bug:
list of updates is generated by UpdateCenter.getUpdates();
UpdateCenter.getUpdates() ->(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites.
UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version.
That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site.
I don't know the best way to fix it while preserving architecture integrity, so I ask someone to fix it.
UPD.
I put this comment's body into the issue description, so it might be deleted now, but I have not such permissions.