[JIRA] [core] (JENKINS-33299) Setup dialog must get list of plugins from update site
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-33299 Setup dialog must get list of plugins from update site Change By: Kohsuke Kawaguchi Labels: 2.0 -rejected Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33299) Setup dialog must get list of plugins from update site
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-33299 Re: Setup dialog must get list of plugins from update site At this point I assume this is going to be post 2.0 GA Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33299) Setup dialog must get list of plugins from update site
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-33299 Setup dialog must get list of plugins from update site Issue Type: New Feature Assignee: Unassigned Components: core Created: 03/Mar/16 3:50 PM Labels: 2.0 Priority: Major Reporter: Daniel Beck Current versions of Jenkins 2.0 bundle the list of plugins with them. As the setup dialog does not work without access to the update site, the list of plugins should provided by the update site. This facilitates changes over time as e.g. Plugins determined to be broken/unsafe/otherwise not suitable for initial setup, replacing plugins that have been removed from the update site, etc. As many Jenkins users may deliberate install older Jenkins versions (including LTS releases which are between 2-6 months old), just updating the bundled data is insufficient. The URL to this file would be resolved relative to the existing URL to the update center (I think the tool installers work like this as well). Server-side, this could be as simple as a static JSON file placed next to the others in the update site. If no file is found, plugin setup should be skipped, and
