So I'm doing something that's a little backward from a standard implementation of a capistrano script.
First, it's not for deploying a Rails app. Second, the cap script *gets* triggered by something else, in this case, after a successful commit to a Perforce repository. What the script does (successfully) is hop onto one of our sandbox servers and update the perforce repository there after a developer makes a commit to the main Perforce repository. The capistrano file works fine when executed from the command line by hand. The problem is that we'd like this to be used by the Perforce after- commit trigger. The problem that arises from this is that Perforce considers a trigger script to be "successful" only if it returns 0 at completion. For whatever reason, Perforce believes that the cap script does not finish successfully (it does). Does anyone know how to control the final output of a capistrano script, to be able to return a 0, or anything else that might be useful in figuring out this problem? (This problem also occurs when running "cap -q" on the script as well.) Thanks for your help, Casey --~--~---------~--~----~------------~-------~--~----~ 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.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
