I am a lone developer most of my time, working on a number of big, mainly PHP-based projects. I want to professionalize and automate how changes to the code base are handled, and create a Continuous Integration process that makes the transition to work in a team possible without having to make fundamental changes. 

What I am doing right now is, I have a local test environment for every project; I use SVN for each project; changes are tested locally, and then transferred to the on-line version, usually via FTP. API documentation is generated manually from the source code; Unit tests are something I am getting into slowly, and it&#39;s not yet part of my daily routine.

The &quot;build cycle&quot; I am envisioning would do the following:

  * A changeset gets checked into SVN after having been tested locally.

  * I start the build process. The SVN HEAD revision gets checked out, modified if necessary, and made ready for upload.
 
  * API Documentation gets generated automatically - if I haven&#39;t set it up in detail yet, using a default template, scanning the whole code base.

  * The new revision is deployed to the remote location via FTP (Including some directory renaming, chmodding, importing databases, and the likes.) This is something I already like [phing][1] for very much, but I&#39;m open for alternatives of course.

  * Unit tests residing in a predefined location are run. I am informed about their failure or success using E-Mail, RSS or (preferably) HTML output that I can grab and put into a web page.

  * (optionally) a end-user &quot;changelog&quot; text file in a pre-defined location gets updated with a pre-defined part of the commit message (&quot;It is now possible to filter for both &quot;foo&quot; and &quot;bar&quot; at the same time). This message is not necessarily identical with the SVN commit message, which probably contains much more internal information.

  * Stuff like code metrics, code style checking and so on are not my primary focus right now, but on the long run, they certainly will. Solutions that bring this out-of-the-box are very kindly looked upon.
 

I am looking for

  * **Feedback and experiences** from people who are or were in a similar situation, and have successfully implemented a solution for this

  * Especially, **good step-by-step tutorials and walkthroughs** on how to set this up

  * Solutions that provide **as much automation as possible**, for example by creating  a skeleton API, test cases and so on for each new project.

and also

  * **Product recommendations**. What I know so far is [phing][2]/ant for building, and [phpUnderControl][3] or [Hudson][4] for the reporting part. I like them all as far as I can see, but I have of course no detailed experience with them.


I am *swamped* with work, so I have a strong inclination towards simple solutions. On the other hand, if a feature is missing, I&#39;ll cry about it being too limited. :) Point-and-click solutions are welcome, too. I am also to commercial product recommendations that can work with PHP projects.

**My setup**

I am working on Windows locally (7, to be exact) and most client projects are run on a LAMP stack, often on shared hosting (= no remote SSH).
I am looking for solutions that I can run in my own environment. I am ready to set up a Linux VM for this, no problem. Hosted solutions are interesting for me only if they provide all of the aspects described, or are flexible enough to interact with the other parts of the process.

&gt; **Bounty**
&gt; I am accepting the answer that I feel will give me the most mileage. There is a lot of excellent input here, I wish I could accept more than one answer. Thanks everyone!


  [1]: http://phing.info/
  [2]: http://phing.info/
  [3]: http://phpundercontrol.org/about.html
  [4]: http://hudson-ci.org/  

All Phpundercontrol Solutions on Gang of Coders

Total of 1 Phpundercontrol Solutions

Setting up a deployment / build / CI cycle for PHP projects