Really nice, I tried it out on a clean setup and it worked well. (existing setup hit an issue which I'm sure wouldn't be hard to sort).
SQLite seems like it could be a good fit. One thought around it though is it would be great to improve the Jenkins HA story allowing multiple controllers to operate like they are one controller. If files remain on the file system I'm not sure if we can do that. But this could be a good stepping stone towards that or at least a great improvement overall. Nice work :) Thanks Tim On Mon, 4 Apr 2022 at 01:01, mike cirioli <[email protected]> wrote: > This is very cool! > > On Sun, Apr 3, 2022, 2:21 PM Alexander Brandes <[email protected]> > wrote: > >> That sounds impressive! Your prototype implementation looks much >> promising, thanks for dropping the link here! >> >> ~ Alex >> >> On Sunday, 3 April 2022 at 18:23:37 UTC+2 [email protected] wrote: >> >>> 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/199c4098-ddcc-4e98-ad81-d927ba28ca07n%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/199c4098-ddcc-4e98-ad81-d927ba28ca07n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CAG%2B1t6PW6vQDEeuOoPd-Da65LUf9VnN-8%3Du%2BOaHO%2BHRzpPkZbw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%2B1t6PW6vQDEeuOoPd-Da65LUf9VnN-8%3Du%2BOaHO%2BHRzpPkZbw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAH-3Bid4MVW2bMCQB_UmWBbMabjVGGdA%3DJ6s4-GppYYtT_qOog%40mail.gmail.com.
