On Wed, Aug 19, 2015 at 9:52 AM, Tom Fennelly <[email protected]> wrote: > I should not post late at night.
I have been guilty of quite rude late-night posts. :-) >> The caveat: you actually know the last version in which global >> configuration was saved (if 1.301+), which is probably close to the >> last version run. If they differ, the last-saved version was very >> likely older than the last-run version—since downgrading core does not >> generally work anyway—so at worst we wind up listing a plugin which >> was split in between those two versions. But such a plugin would have >> been bundled in the later version, and thus already in your plugins >> directory, so we can simply skip over it. > > Where this might cause frustration is if an earlier split plugin was > uninstalled/removed and we end up installing it again, thinking it was split > since the last version (as we know it) Assuming the user saves global configuration at least occasionally (or we could also force a save after changing plugins etc.), this would not occur since the new core upgrade interval would not include the split point. -- 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/CANfRfr2cf_ZebSPxMXWEwh_XJiBSpoB%2B-HnPjXpv4amCf0rQcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
