Topic: Capistrano task – better cap deploy:pending

I wanted a quick capistrano task to show information about whats running on each of our servers. I also needed to know what would would change when I ran ‘cap deploy’, in case I pushed something that hadn't passed QA yet.

“cap deploy:pending” and “cap deploy:pending:diff” already solve this problem a little bit, but I found them to be too verbose. Also, they don't work so well as part of an automated deploy process since they can require user interaction.

So I wrote a ‘cap revisions’ task to solve this. It can be run standalone, and when its chained after the ‘deploy’ task it will show a list of the new commits that have just been pushed to the server.

If it sounds interesting, you can read more about it and find the code here: http://www.f-77.com/2011/03/02/capistra … ons-diffs/

Last edited by nathan.f77 (2011-03-02 02:27:17)