I see several problems with this BC breaking approach: - Countless instances will have to use both the DB and the FS as backend simultaneously for some time. If this will span several upgrades, downgrades will be a pain for the whole time. - There are plugins that depend on files heavily. (Copy artifact plugin was not fixed to use ArtifactManager since 1.532 (and as it depends on attributes that are not provided by the abstraction it is a bit tricky)).
My rough estimate is this would require fixing tens of percents of all plugins. Note that I am not suggesting to use the as the persistence API for next 10 years but as a way to ensure all plugins will be DB compatible without rework. -- oliver -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/26501e09-ecca-469a-8038-c0cacf4737d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
