I have never used H2, but I have a strong preference for SQLite. It has been deployed more widely than all other database engines combined and is probably one of the top five most deployed software programs of all time, competing only with zlib, libpng, and libjpeg. It is very high quality code and its tests have 100% branch coverage. These are not small achievements. They mean it when they write: "Small. Fast. Reliable. Choose any three."
Obviously plugins would need to be prepared in advance for such a migration. With the ugly schema from my experiment, not too many preparations are needed. But I suspect that adopting a nice schema backed by an ORM like Hibernate would likely require many changes to the serializable objects. It would be interesting to play around with this, but definitely more than a day's worth of hacking. I haven't thought about build logs too much, but I could see some value to storing them in an SQLite database, if not as the primary storage than at least in a secondary cache for full-text search. -- 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/CAFwNDjr7wMBOtzFBMNTVN5RSWMJTda%2B2Z8-ge6tqdJU4YfWfOA%40mail.gmail.com.
