Check into cruisecontrol.rb. I use it to drive deploy scripts, Tests
via the deploy scripts on remote test clusters, normal ci of source
code checkouts, and I also use it to trigger scheduled actions like
backups and other maintenance scripts. If any of the projects fail
emails get sent, anybody running with cctray gets a growl notice, and
a pair of red and blue police lights go off.
On Feb 25, 2010, at 8:58 AM, Greg Akins <[email protected]> wrote:
On Thu, Feb 25, 2010 at 11:53 AM, Lee Hambley
<[email protected]> wrote:
Cap is a deployment tool, so you shouldn't be intergrating test
runs with
deployment (or automating deployment after successful tests, etc) -
these
practises can be really damaging. (so you'd better know the risks!)
I can appreciate why you'd say that Capistrano shouldn't be
responsible for running tests.
But why not chain deployments after successful test runs..
--
Greg Akins
http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre
--
* You received this message because you are subscribed to the Google
Groups "Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
