I don't have a solution for this, but to be honest, I think this is just way to complicated and just screams for issues in the long run. We should go for less magic and more transparency - I think we should just inform the users about this changes and not try to heal the world. We can also inform the users with an info message right within Jenkins after he updated to a version where no plugins are bundled anymore. ...just my 2cents... /Domi
> Am 18.08.2015 um 23:03 schrieb Tom Fennelly <[email protected]>: > > >> On Tuesday, August 18, 2015 at 10:01:28 PM UTC+1, Tom Fennelly wrote: >> Something I was wondering in order to help with upgrades ... could we use a >> simple plugin that needs to be installed that captures and records all split >> plugin info from the instance. This info can then be used on the subsequent >> install so as to install the exact versions of split plugins. An upgrade >> would be aborted if that info was not present during startup. Or is there a >> better way or existing info that can be used? > > Prob not practical where there's a lot of Masters? > -- > 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/35c09963-21aa-450a-8f47-4e87bb5015d9%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/7DB55897-A5EC-4DBC-8F7E-0F26C21FA6F1%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
