On Wed, Sep 16, 2015 at 1:33 PM, Daniel Beck <[email protected]> wrote: > The issue that caused me to think we may need to keep pinning around is your > change to External Monitor Job 1.4 where a resource was moved from core into > the plugin.
I see. Basically this is what `PinningIsBlockingBundledPluginMonitor` was designed to help with, though it sounds like you are getting some error earlier and more intrusively than that was designed to handle. Can we treat this particular error as a robustness bug? Alternately, be more aggressive and force updates of “split-bundled” plugins newer than an installed version, disregarding historical pinned status (and deleting the existing monitor). I think that is a much more reasonable proposal when we are no longer bundling plugins just for fun, and we are only talking about updating to a version very soon after the split—from 1.0 to 1.0.1, say. > What are we going to do when we notice there's something broken with the > first release of a detached (and therefore compat-bundled) plugin? Fix and > release the plugin, and increase the compat-bundled version? That is what we have done in the past. -- 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/CANfRfr0Fpi_xgG2170M%3DsYkzi8m1Jxn3ZWWdXZ5jjVcx_Unxmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
