> All of these, to me, say that there are fundamental flaws with how Jenkins is > structured from a systems administration standpoint. The most duh/obvious one > is that data is not cleanly separated from configuration making it very > difficult to automate. I don't need to automate the data part (shove it in a > DB > for all I care ;)) but in Puppet I've got tons of well-defined, easily tested > patterns for generating configuration files.
I would add one more architectural choice: having the core scheduler and build execution engine in the same process as the UI. I think this makes it more complex to administer larger and enterprise grade instances. Plus it likely deteriorates stability of the whole system. -- 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/3C350C9D1C9DEE47BAEA43102B433C9EBE5DFDCB%40HQMBX2.ads.eso.org. For more options, visit https://groups.google.com/d/optout.
