Here is an idea that might be crazy but provide a way to switch to another
persistence backed without braking BC.
We build our API around java.io.File, which is causing the majority of
problems with replacing filesystem that I am aware of. Some time ago I
come across TrueVFS, a library that uses File subclasses to fake a
directory hierarchy in compressed archives. One can then manipulate
archive and directory hierarchy transparently.
Can we do whatever PowerMock is doing to hook custom logic into `new File`
and provide custom implementation in case it is one of the files we decide
to store in DB (whole JENKINS_HOME?) and JDK implementation for the rest?
This would allow users turn it on when/if they are ready. It will also
give us a lot more time to design suitable persistence API without
breaking the existing one.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/op.x6f8yuensbfict%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.
