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

[Daniel Pötzinger]

Hey Robert

Yes please - would be good if you can update me since i am also interested if you and the book came up with better ideas.

Greetings



-----Ursprüngliche Nachricht-----
Von: typo3-team-core-v5-bounces at lists.typo3.org [mailto:typo3-team-core-v5-bounces at lists.typo3.org] Im Auftrag von Robert Lemke
Gesendet: Montag, 12. April 2010 11:38
An: TYPO3 v5 Core Team
Betreff: Re: [TYPO3-team-core-v5] Phoenix Continuous Integration Builds

Hi Daniel,

I suggest that Karsten and I add / modify the story [1] a bit during this week as I currently have all the ideas from the Continuous Delivery book loaded into my brain (well, most of them) and Karsten and I will work on build scripts this week anyway (integration / release script for FLOW3).

We'll keep you updated and @Sebastian, we'll talk to you as soon as we have some more concrete tasks / suggestions.

Cheers,
robert

[1] http://forge.typo3.org/issues/show/7215

Am 12.04.2010 um 10:50 schrieb Karsten Dambekalns:

> Hi.
> 
> On 10.04.2010, at 11:55, Sebastian Kurfürst wrote:
>>> Is it also ok to push the build scripts inside the project, e.g. in a build folder?
>>> (This way the buildscript is versioned with the project itself.)
>> I'm not fully sure if that's such a good idea... The main reason is that
>> I'd like the infrastructure for Selenium Tests, Unit Tests, Integration
>> Tests, ... to be built in such a way that it's not only usable for the
>> "main TYPO3 v5" project, but also for other packages / distributions who
>> wish to use it, so for purely community-driven packages as well.
> 
> Maybe (tiny) parts of the build script can be reused, but in general it is the only feasible idea to have the build scripts for a project versioned with the project itself. Take a look at the continuous deployment book Robert recently recommended. :)
> 
> The build scripts will not only be about running tests, but also deal with packaging and deployment. Probably a unified approach for extensions and/or packages is possible (and would be maintained in hudson-helpers), but the distinct projects need their very own build system.
> 
> I started with build scripts for FLOW3 that will be the base for Phoenix as well, the current (work in progress) results are in the FLOW3 Base distribution SVN. Currently the phing script can
> * run PHPUnit (including code coverage)
> * run metrics (PHPMD, PHPCPD)
> * build API documentation using PHP_UML
> I tried to modularize the Phing buildfiles, so parts can be reused. Sebastian, feel free to suggest a more reusable set of naming and/or fileset conventions, so we can reuse the more common buildfiles.
> 
> Regards,
> Karsten
> -- 
> Karsten Dambekalns
> Gimme Five!
> http://typo3.org/gimmefive
> 
> 
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5

_______________________________________________
TYPO3-team-core-v5 mailing list
TYPO3-team-core-v5 at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5