<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 15 May 2008 22:32:30 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Michael Kimsal's Blog: PHP Continuous Integration with phpUnderControl]]></title>
      <guid>http://www.phpdeveloper.org/news/10054</guid>
      <link>http://www.phpdeveloper.org/news/10054</link>
      <description><![CDATA[<p>
<i>Michael Kimsal</i> has <a href="http://michaelkimsal.com/blog/continuous-integration-with-phpundercontrol/">put together</a> a <a href="http://michaelkimsal.com/blog/php-continuous-integration-with-phpundercontrol/">small page</a> to help you get started using the phpUnderControl continuous integration system:
</p>
<blockquote>
If you're not using phpUnderControl, you owe it to yourself to check it out, as I think 'continuous integration' will likely change the way you think of development.  I've used CruiseControl in the past for PHP, but the PHP-specifics phpUnderControl brings to the project are too much to pass up.
</blockquote>
<p>
The <a href="http://michaelkimsal.com/blog/php-continuous-integration-with-phpundercontrol/">page</a> mentions some of the common issues you might have in getting started - installation problem, the use of the PHP Code Sniffer and the Project Mess Detector from <a href="http://www.phpunit.de">PHPUnit</a>.
</p>]]></description>
      <pubDate>Mon, 28 Apr 2008 11:18:20 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Raphael Stolt's Blog: Hooking a Growl publisher plugin into Xinc]]></title>
      <guid>http://www.phpdeveloper.org/news/9998</guid>
      <link>http://www.phpdeveloper.org/news/9998</link>
      <description><![CDATA[<p>
<i>Raphael Stolt</i>, with some time on his hands, set up a local copy of <a href="http://code.google.com/p/xinc/">Xinc</a>, the "shiny new Continuous Integration(CI) server" as hosted on the Google code site and spent some time working with it:
</p>
<blockquote>
Since then the idea of building a Growl publisher plugin for Xinc was traveling my mind repeatedly, so the following post will break this circle and show a possible approach to build such a plugin, which can be used to notify the build result for continuously integrated projects and thereby provide an on-point/immediate feedback.
</blockquote>
<p>
He includes <a href="http://raphaelstolt.blogspot.com/2008/04/hooking-growl-publisher-plugin-into.html">the plugin class</a> (ready for cut&paste) as well as the task definition and how to hook it all in to the Xinc build system. There's also a little example of it in action - a happy/sad indicator showing if the build failed or was a success, right there on the desktop.
</p>]]></description>
      <pubDate>Fri, 18 Apr 2008 12:59:47 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: On PHPUnit and Software Metrics]]></title>
      <guid>http://www.phpdeveloper.org/news/9589</guid>
      <link>http://www.phpdeveloper.org/news/9589</link>
      <description><![CDATA[<p>
In one of his latest entries, <i>Sebastian Bergmann</i> <a href="http://sebastian-bergmann.de/archives/744-On-PHPUnit-and-Software-Metrics.html">answers a question</a> from another blogger about the future of <a href="http://sebastian-bergmann.de/archives/689-PHPUnit-and-Software-Metrics.html">software metrics</a> and <a href="http://sebastian-bergmann.de/archives/690-PHPUnit-as-a-Project-Mess-Detector.html">project mess detection</a> as a part of the <a href="http://www.phpunit.de">PHPUnit</a> project.
</p>
<blockquote>
When I started to work on these projects, there was no other place for me then to develop them as part of PHPUnit. [...] But the more I thought about it, I realized that these features do not belong into PHPUnit but into a suite of tools that PHPUnit is a well-integrated part of.
</blockquote>
<p>
He did, however, include it as a part of the <a href="http://sebastian-bergmann.de/archives/720-PHPUnit-3.2.html">PHPUnit 3.2</a> release at that time. Now, however, there are the tools and platforms to make those tests useful outside of the PHPUnit environment and is allowing him to <a href="http://www.phpunit.de/changeset/2377">move it out</a> from the testing application and on to <a href="http://www.phpunit.de/changeset/2351">closer integration</a> with other software.
</p>]]></description>
      <pubDate>Fri, 08 Feb 2008 09:31:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Support for PHPUnit in Parabuild]]></title>
      <guid>http://www.phpdeveloper.org/news/8464</guid>
      <link>http://www.phpdeveloper.org/news/8464</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> <a href="http://sebastian-bergmann.de/archives/691-Support-for-PHPUnit-in-Parabuild.html">quickly notes</a> the support that's been added to <a href="http://www.viewtier.com/products/parabuild/index.htm">Parabuild</a> for PHPUnit:
</p>
<blockquote>
<a href="http://www.viewtier.com/">Viewtier Systems</a> is looking for testers of their new <a href="http://www.viewtier.com/products/parabuild/eap/phpunit.htm">support</a> for <a href="http://www.phpunit.de/">PHPUnit</a> in their <a href="http://www.viewtier.com/products/parabuild/index.htm">Parabuild</a> software build and release management system. I am excited that a company such as Viewtier Systems realizes that there is a market for their product in the PHP space and adapts their tool to work well with existing tools such as PHPUnit in that space.
</blockquote>
<p>
<a href="http://www.viewtier.com/products/parabuild/index.htm">Parabuild</a> is a software build and release management system that helps software teams and organizations reduce risks of project failures by providing Continuous Integration and delivering practically unbreakable nightly builds.
</p>
<p>
If you would like to sign up as a beta tester, <a href="http://www.viewtier.com/products/parabuild/eap/phpunit.htm">all of the information is here</a>.
</p>]]></description>
      <pubDate>Thu, 16 Aug 2007 09:14:00 -0500</pubDate>
    </item>
  </channel>
</rss>
