in reply to Perlish alternative to CruiseControl (automated builds)?

Generally, you cron the script that does that sort of detection. So, if there's any decisions to be made, you have to write the script ot make that decision. cron just runs the thing.
My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • 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 21:24 UTC

    Right, I think I see what you mean: cron the make command directly, and then right after that cron a script that checks if there's any new email.

    Thanks.

[reply]
      Uh, no. Write a script that does everything (run make, check email, etc). Cron that.
      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]

        Or add a make target which depends on a successful build and test and mails any results, then run that directly from cron.

[reply]

In Section Seekers of Perl Wisdom