I would love to see bundled/pinned plugins to go away and removing some
bundled plugins without introducing new ones sounds like a good plan to me.
What I would like to see implemented eventually is a support for custom
plugin collections: Simple list of plugins (with minimal versions,
perhaps) to be proposed to user and installed with one click distributed
online as a single file / base64 encoded string. Everybody, can easily
share what they use: "Hey, check out my .NET development tooling!".
With that in place, Jenkins can be distributed with simple 'default'
collection preconfigured that can change in time following current trends
/ user needs. The same way user is invited to create first job, we will
invite users that have not installed any plugin so far to install
recommended plugins. Admittedly, this is a step towards setup wizard...
--
oliver
--
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/op.x21eqovzsbfict%40arch.
For more options, visit https://groups.google.com/d/optout.
