Version control and continuous integration

Version Control

EZPDO used to use the CVS server at sourceforge.net. Now its code base has been migrated to Subversion.

Continuous Integration

EZPDO adopts the idea of Continuous Integration. See this for more info on Continous Integration. The tool we use is called Rephlux by Jon Ramsey. Thank you, Jon!

Rephlux runs nightly on EZPDO. Any CVS commits since the last run will trigger Rephlux to run the EZPDO test suites. If all tests pass, it publishes the latest tarball and zipball.

Revisions and failed tests can be viewed in the Rephlux log. Please note that after the migration from CVS to SVN, new build log can be found at http://www.ezpdo.net/log/latest.php.

3 user comments

  1. EZPDO » Blog Archive » EZPDO in the last week on March 19th, 2005:

    […] o need to make some configuration changes in the testing suites to include them in nightly Rephlux. We’d also want to collect more user feedbacks and prioritize outstanding issues and feature reques […]

  2. EZPDO: An O/R Mapping and Persistence Solution for PHP5 on April 28th, 2005:

    […] pects. The following is a short summary apart from the fixes annouced in the pre-1.0 post. The Rephlux log may provide you more detailed info on the changes. EZPDO is now made a […]

  3. dardo on June 19th, 2007:

    Title says “Versiont control”, I think it should be “Version control”.

Post your comments

XHTML: tags you can use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Couldn't find your convert utility. Check that you have ImageMagick installed.