Kind of off topic, but it would really be nice to be able to "pin" a plugin to a specific version that won't get upgraded.
On Thu, Aug 11, 2016 at 11:08 AM Daniel Beck <m...@beckweb.net> wrote: > > > On 11.08.2016, at 15:14, Jason Kulatunga <darkmeth...@gmail.com> wrote: > > > > I'm not sure if anyone has done something similar but I wanted to get > some feedback before I spent too much time investigating either idea. > > Note that pinning doesn't prevent a plugin from being upgraded -- it's > related to Jenkins 1.x plugin bundling, and means that a plugin that's also > bundled (e.g. subversion) won't get overwritten by the version bundled with > Jenkins on startup. In Jenkins 2, it's basically irrelevant. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/3C393994-86E4-4048-9D99-2A4A258706BE%40beckweb.net > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdCMKhe0ka_j1OMOU9XxkaXBVihJDhvjg207BgoQ%2BtBEQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
