Just a follow up to thank everyone who gave me input on this thread.
I opted to setup a jenkins instance, and, while the initial effort to get
it configured for our codebase was nonzero (she says four weeks after
the initial post), we're now very happy to have a unified standard for
"does this code pass muster?" It doesn't solve the problem i thought i
had ("how do i keep each dev from having to stand up his own snowflakey
AMP stack?"), but it solves the problem i did have, since now we have
a place everyone can go to look at test results which were run in a
consistent way. If people have home setups that are robust enough that
they can run tests at home too, that's gravy, but, if not, they can
still develop.
BTW, someone suggested docker, which looks neat, but which uses vagrant
under the hood. I still like vagrant on a mac a bunch for my own use,
but windows users found it hard to get my vagrant/puppet config running
at all consistently.
Cheers.
Chaos
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
