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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9d9e1968-b7c7-4296-899c-f2b05f10ac6a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
