I had in mind to hack into jenkins AbstractItem#load & save so it create the xml content but also store in some fast storage format, then on load would compare xml timestamp to ensure the fast storage is in sync. IIRC apache cxf uses this to load FastInfoset spring xml configuration.
Need to experiment with this, but I guess this can make Jenkins bootstrap quicker while not breaking compatibility for the few plugins to rely on actual files (sic). 2015-10-07 19:39 GMT+02:00 Kohsuke Kawaguchi <k...@kohsuke.org>: > Right, I remember looking at DotCi and thinking that the way it moved the > storage to mongodb points toward an abstraction we can build. > > Similar hook already exists for artifacts, and then we can provide > auxiliary BLOB store for plugins that write random bits of data under > builds, jobs, etc. > > Over time we can move things one by one to the BLOB store like that, then > at that point we have filesystem free Jenkins. > > > 2015-10-06 11:18 GMT-07:00 Surya Gaddipati <suryapraka...@gmail.com>: > >> Regarding backend solution. We use DotCi and store all builds/logs in >> mongodb.( Still experimenting how to properly store logs in the db, but we >> have it working on staging). >> >> The only things on disks are plugins and folder config.xml ( because of >> this issue https://github.com/jenkinsci/jenkins/pull/1762, jenkins >> deletes anything not on disk from memory ). I need to spend time to fix the >> issue in jenkins properly. >> >> >> Once that is done. We can have things like, deploying on heroku , true >> load balancing with multiple masters. >> >> One more thing that is preventing from from jenkins from being used in >> any serious installations is heavily thread locked Queue implementation. We >> are having to do strange workarounds with our jenkins because it >> threadlocks under even medium loads ( I saw this mentioned in google's >> slides for JUC too, curious what their solution was ) . >> >> An extension point for queue would be great so we can store queue in >> redis or something. >> >> >> Surya >> >> -- >> 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/9d9e1968-b7c7-4296-899c-f2b05f10ac6a%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/9d9e1968-b7c7-4296-899c-f2b05f10ac6a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Kohsuke Kawaguchi > > -- > 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/CAN4CQ4zpgWrGyuE0KkfKejMxSVuXNgabdL6K5XTnZRo5k1uAhg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4zpgWrGyuE0KkfKejMxSVuXNgabdL6K5XTnZRo5k1uAhg%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzkg3t3H7v%3DB5MDjEQ1ns1HeZp_zZyg8kB7Zs3cTiuXzFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
