On the Symfony project blog there's an announcement posted about changes in the framework to allow for reproducible builds.

Reproducible builds are a set of software development practices that create "a verifiable path from human readable source code to the binary code used by computers". In other words, if you don't change the source code, the compilation result should always be exactly the same.

Explained more simply in the case of Symfony: if you build the container and warm up the cache of the same unchanged application multiple times, the result should always be the same.

The post talks about the idea of "reproducible builds" and how they should be "completely deterministic" where the end result is always the same (no random data, no auto-generates date/times). A few changes were required to the framework to ensure these builds were possible. The post lists out these updates and links to the bug reports for each.

In this blog entry on Sebastian Nohn's site, he explains how to use CruiseControl, Ant, and PHPUnit to provide continuous builds for your application.

An important part of any software development process is getting reliable builds of the software. Despite it's importance, we are often surprised when this isn't done. We stress a fully automated and reproducible build, including testing, that runs many times a day. This allows each developer to integrate daily thus reducing integration problems.

This blog posting will show you how to enable continuous builds with CruiseControl, Ant and PHPUnit. But be warned: Continuous builds are addicting.

They step you through the process - the installation of the needed packages, working with Ant, getting it to talk to Cruise, and the integration of PHPUnit. Finally, they work in a method to notify others (in this case, the management) when successful builds have been compiled.

In this blog entry on Sebastian Nohn's site, he explains how to use CruiseControl, Ant, and PHPUnit to provide continuous builds for your application.

An important part of any software development process is getting reliable builds of the software. Despite it's importance, we are often surprised when this isn't done. We stress a fully automated and reproducible build, including testing, that runs many times a day. This allows each developer to integrate daily thus reducing integration problems.

This blog posting will show you how to enable continuous builds with CruiseControl, Ant and PHPUnit. But be warned: Continuous builds are addicting.

They step you through the process - the installation of the needed packages, working with Ant, getting it to talk to Cruise, and the integration of PHPUnit. Finally, they work in a method to notify others (in this case, the management) when successful builds have been compiled.