delete a golden file on the server when failure happens. ( Make sure you copy the file from a known location before the start of the task.) You can even seperate concerns by using new before feature in Cap2. I love Cap 2 when it comes to deployment and automation. Then look for it using the following command. run "ls -l filename"
If the file is not found the error code returned is 1. I have used this value for error checking and to report failure in an automated way. On Jan 3, 11:17 am, RubySmith <[EMAIL PROTECTED]> wrote: > I'd greatly appreciate if any of you could point me to a book/tutorial/ > doc > on how to do robust error checking with Cap 2 recipes? > > In my case I have 4 tasks. When I call the first task it > automatically calls rest of the tasks one after the other. > > How can I test whether previous task completed before proceeding > with next task. > > Are there any DSL commands like exit, check_error > > Can i rely on $_ and if true how can mix Ruby code with Cap receipe? > > Thanks a lot in advance, > -p --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
