Re: Minutes for PEAR Group Meeting 2008-10-05

Hello Daniel, > The Continuous Integration side of things; what are the plans; who's > driving them? I am/was the one driving the things. Original intention was to get a pear-wide test suite so all packages with unit tests could be tested at once. Result of this was the AllTests.php in pear's cvs module root. This script does a dirty trick to ensure all packages can be run without installation: It symlinks directories so that it seems as if the package was installed and all files can be accessed in their normal path. While this makes it easy to run the suite, it's a hack. Second problem is that all tests are run in a row. When on test makes a fatal error, the whole suite suffers. This might change with PHPUnit4 and test forking, but it does not work now. What I'm a little proud of is the phpt integration into phpunit. The next two tools are, as you know, the documentation coverage and the daily phpcs runs. The suite could and should be made better, but I'm too occupied with the peardoc transition at the moment. If someone would take it over, I can give you ssh access to my server. I planned to convert all my shell scripts to phing, but didn't get really far. The scripts are in pear's svn, sandbox/QA_PEAR_CI. The doc coverage code is in PEAR itself, QA_PEAR_Coverage or so. Some files could also lurk around on my own svn server, svn.cweiske.de in "tools" or "php" (public read access). -- Regards/Mit freundlichen Grüßen Christian Weiske -= Geeking around in the name of science since 1982 =-

Attachment: [application/pgp-signature] signature.asc