How easy is it in Hudson to just build .zip or tar.gz files of a ZF project? - Robert
_____ From: Eric Marden [mailto:[EMAIL PROTECTED] Sent: 02 May 2008 22:00 To: [email protected] Subject: RE: [fw-general] Nightly build system Continuous Integration is a highly customized process - use what works. The process looks different at every company/organization/team. We're building ours around Hudson (https://hudson.dev.java.net/ <https://hudson.dev.java.net/> ). -- Eric Marden _____ From: Robert Castley [mailto:[EMAIL PROTECTED] Sent: Friday, May 02, 2008 4:54 PM To: [email protected] Subject: RE: [fw-general] Nightly build system Phpundercontrol looks pretty neat. But I am a simple man with simple needs (and not a huge Java fan!). Too much bloat IMHO. Scripts, for me, seem to be the way forward. I can automate these with a cronjob. The script syntax I am going for is: - Export from CVS - pack my CSS & JS (using YUI Compressor) - OK, I use Java here :-) - remove source CSS and JS files - Create .zip and .tar.gz - remove CVS exported directories Thanks for everyones input, interesting to learn how others do it. Maybe it's time to rewrite Trac in ZF :-) - Robert -----Original Message----- From: Jeffrey Sambells [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: 02 May 2008 21:39 To: Zend Framework General Subject: Re: [fw-general] Nightly build system I've set up phpUnderControl (http://www.phpundercontrol.org/ <http://www.phpundercontrol.org/> ) which encompasses the below tools. Took me a short afternoon to figure out but once I did it works awesome and is easy to use. Our bugtracking, SVN and DB use other separate tools that are not related but I rely heavily on phpUnderControl for reporting so make sure we're all doing a good job. We've even converted our documentation process to something similar to ZF so that the manual is built with every build too. Though some of my developer would rather not have the CodeSniffer reporting :) - Jeff On 2-May-08, at 2:05 PM, Josh Team wrote: > Do you disagree with the notion then that building a reusable set up > with: > CruiseControl > PHPCodeSniffer (PEAR) > PHPUnit > PHPDoc > > and maybe your own scripts rather shell or php to integrate them all > together is as "simple" to use for the common, non-elaborate, shop > though? > > Take into account now bug tracking, subversion control, database table > structures in the migrations, etc. > > On Fri, May 2, 2008 at 11:59 AM, Marco <[EMAIL PROTECTED]> wrote: > I use Cruisecontrol in collaboration PHPCodeSniffer, PHPUnit, PHPDoc > to generate both unit test suite results, API documentation and coding > standards violation reports etc. > > I've found it works very well for both automated nightly builds and > also on request builds using a simple web interface. > > Regards > > Marco > ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________ ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________ ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________ ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________
