Re: Perlish alternative to CruiseControl (automated builds)?

The first thing that comes to mind is to just have a cron task that runs make on my Makefile. However, how can I programmatically detect if the build fails and jump to my send_email script?

Dunno about yours, but my cron tends to email me every time something exits with a non-zero exit status. GNU Make would be among the programs that exits with meaningful status.

Other than cron, I'd look at the new and exciting IPC::System::Simple, possibly combined with Net::SMTP::OneLiner. Suddenly it seems like a four line program to me.

-Paul

Comment on Re: Perlish alternative to CruiseControl (automated builds)?

Replies are listed 'Best First'.
Re^2: Perlish alternative to CruiseControl (automated builds)? by Anonymous Monk on May 27, 2008 at 18:24 UTC
Ah, of course. `make` exits with its own non-zero status if one of the commands it runs exits with a non-zero status. And thus, `cron` would -- as expected -- send an email. So, it looks like all I'd need to do to get a web interface at that point would be: write a CGI script to check for new email and go from there. Thanks!	[reply]
Re^3: Perlish alternative to CruiseControl (automated builds)? by jettero (Monsignor) on May 27, 2008 at 18:31 UTC
I missed that about the webetface. Really, you could just store the output of the command in a database and have a status feel so obsessive web refreshers could see when it completes... Or, you could do something like what merlyn did here: http://www.stonehenge.com/merlyn/PerlJournal/col01.html or here: http://www.stonehenge.com/merlyn/LinuxMag/col39.html -Paul	[reply]