3. Continuous
Integration
Subversion
forge.typo3.org
Collaboration
Platform
Wiki Bugtracker
4. Abstract
{
Version Control
Requirements
Test-Driven Development
{
What is CI?
Continuous Integration with forge
Integration
Your own CI Server
Conclusion
5. - Requirements -
Version Control
Subversion
Repository
Commit Update Update
10. How many of you write
unit tests during your
daily work?
11. Test-Driven
Development
» ... means that you write an automated
test, then you write just enough code to
make that one test pass, then you
«
refactor the code primarily to improve
readability and remove duplication.
Henrik Kniberg
SCRUM and XP from the Trenches
12. Test-Driven
Development
Test Case FAIL Implementation OK Refactoring OK
25. Continuous Integration
» ... is a software development practice where
members of a team integrate their work
frequently. Each integration is verified by an
automated build (including test) to detect
integration errors as quickly as possible.
Many teams find that this approach leads to
«
significantly reduced integration problems and
allows a team to develop cohesive software
more rapidly.
Martin Fowler
http://martinfowler.com/articles/continuousIntegration.html
39. Your own CI server
3
Check out our build scripts:
https://svn.typo3.org/Teams/forge.typo3.org/hudson-helpers/
40. Your own CI server
4
Use the following „execute shell“ build target:
cd /path/to/hudson-helpers
phing/phing/phing -f build.xml all -Dpackage=PACKAGE_KEY