On Sun, Aug 23, 2015 at 2:47 PM, Sacha Labourey <[email protected]> wrote: > This setup makes the (high) availability > (and bandwidth capacity) of the "update" center (the "setup" center in that > scenario) a key requirement (center down => no install of Jenkins is > possible anymore).
http://updates.jenkins-ci.org/ is already mirrored and the servers are expecting heavy traffic. And with the _current_ WAR you already need to hit the UC just to get, say, Git support. So I do not think this is a reason to bloat the standard download. It is always possible to produce an ISO image of Jenkins with the top 200 plugins preinstalled for overnight mailing of CDs to benighted regions of the world, such as central Massachusetts. :-) Also I agree with Daniel that we should not “check by default” traditionally bundled plugins without a good reason, i.e., other than compatibility for upgrades of split plugins. How many people really use `external-monitor-job`, or even know what it does? This is just a feature that Kohsuke at some point (years ago) decided would be neat to implement, and happened to put in core. Certainly does not have as broad appeal as, say, `matrix-project` (currently bundled), or `cloudbees-folder` (currently not). Yet it clutters everyone’s _New Item_ screen with a mysterious option. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1hk2F1jG2N5r921UgnUB3XtfaqG-j58%2BYFEu53vMGcYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
