I've been playing around with Blueprint  because I like the idea of being able to dip a toe in without plunging in the deepend with Chef/Puppet.
BryantD, if you work in a place where testers review Puppet manifests that's awesome. It's fair to say I was generalising. I believe that the tools should be doing more to encourage it.
In my talk at the last GDC Online, I called for technical operations groups to engage QA in testing their tools: puppet manifests, cobbler installations, whatever. If I thought everyone was doing it I would have left that slide out.
I am not currently in a position which has me evaluating tools, but you are now on my list of tools to look at. I will admit it'd be nice to be able to give testers friendlier interfaces.
Can you provide an example of what that means? E.G. What should Jenkins be doing differently to encourage sysadmins to use it? What should Puppet be doing differently to encourage developers to use it?
"Do sysadmins typically contribute to Jenkins projects?"
Tools are what you make of 'em, man.
[asterisk] Featured Pin Factory in the Division of Labour (it was a hot startup, sweeping the 1776 Crunchies)