[TYPO3-team-core-v5] Phoenix Continuous Integration Builds

[Daniel Pötzinger]

Hey all

Here my ideas for a first CI setup for phoenix - following the best practices that we find out for our self:

SVN:
--------
I dont know the ideas for the Distribution well, maybe you could explain.
Here my 2 cents:
- the build scripts for all builds should be in svn
- maybe its useful to have a new Distribution https://svn.typo3.org/FLOW3/Distributions/phoenix ?


at least Two environments are required:
-----------------------------------
* integration_dev with own domain for fe access
  *building form the "phoenix" trunk 
  *using (svn externals) to FLOW3, TYPO3 5.0 and the Demopackage that we want to build up
       * each pointing to the trunk

* integration with own domain for fe access
   * building from the latest/defined tag
   * using also tagged packages and not trunk of packages


Build Setups in Hudson:
-----------------------------------

1) phoenix-integration_dev_commit
* Quick build that is triggered by SVN commits. 
* build xml just checkout the packages and run the basic unit tests

2) phoenix-integration_dev_full
* triggered nightly
* build that builds from scretch (empty folder):
* build xml:
  * svn checkout of phoenix trunk
  * fill the contentrepository with a CR dump
  * system specific configurations (property file)
  * run unit tests
   * run integration unit tests and selenium tests

3) phoenix-integration_dev_tests and 4) phoenix-integration_tests
* triggered manual only running the selenium tests


5) phoenix-integration_full
* triggered manual (at en of sprint for instance)
* simelar to phoenix-interagtion_dev_full but 
   * as the first step it tags the relevant packages
   * it tags the phoenix and adjust svn externals to new tag
   * then it builds from tag


later a 6) phoenix-integration_release may do the additional steps for releasing (releasenotes...)


Waiting for feedback

Daniel Pötzinger