Hi Domi. When you say "I don't have a solution for this", I think you are referring specifically to the issues around upgrades and split plugins, right?
Wrt split plugins, I think the problem for a user doing an upgrade would be that they might not know exactly which split plugins they now need to install (that they are now missing), having done an upgrade. We could give them a message/warning telling them to "install split plugins" (or however it would be worded), but it probably wouldn't be a lot of help to them. I'd imagine it might be a "What the F***" moment for them. T. On Wednesday, August 19, 2015 at 7:17:56 AM UTC+1, Dominik Bartholdi wrote: > > 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] > <javascript:>>: > > > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/35c09963-21aa-450a-8f47-4e87bb5015d9%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/35c09963-21aa-450a-8f47-4e87bb5015d9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/1e0051ef-417d-49c0-827d-1166bfa10c4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
