I've set up phpUnderControl (http://www.phpundercontrol.org/) which
encompasses the below tools. Took me a short afternoon to figure out
but once I did it works awesome and is easy to use. Our bugtracking,
SVN and DB use other separate tools that are not related but I rely
heavily on phpUnderControl for reporting so make sure we're all doing
a good job. We've even converted our documentation process to
something similar to ZF so that the manual is built with every build
too.
Though some of my developer would rather not have the CodeSniffer
reporting :)
- Jeff
On 2-May-08, at 2:05 PM, Josh Team wrote:
Do you disagree with the notion then that building a reusable set up
with:
CruiseControl
PHPCodeSniffer (PEAR)
PHPUnit
PHPDoc
and maybe your own scripts rather shell or php to integrate them all
together is as "simple" to use for the common, non-elaborate, shop
though?
Take into account now bug tracking, subversion control, database
table structures in the migrations, etc.
On Fri, May 2, 2008 at 11:59 AM, Marco <[EMAIL PROTECTED]> wrote:
I use Cruisecontrol in collaboration PHPCodeSniffer, PHPUnit, PHPDoc
to generate both unit test suite results, API documentation and
coding standards violation reports etc.
I've found it works very well for both automated nightly builds and
also on request builds using a simple web interface.
Regards
Marco
