FEATURES/PROBLEMS: * Failure is incredibly ungraceful, though generally unlikely, given that the requirements for accessing the Trac site are roughly the same as those for accessing the repository. * Currently, the trac user/pass must be the same as the SCM user/pass. It remains to be seen how much of a problem this will be. == SYNOPSIS: Include the recipes: require ‘capistrano_trac/recipes’ For the trac tasks to work, the :trac_url variable must be set to the root of your trac site. For example: set :trac_url, "
; The 2 trac ticketing tasks are designed to be run in conjunction with a deployment or rollback, although this isn’t mandatory. To automatically document deployments and rollbacks in your capistrano deployment, add the lines: * after "deploy", "trac:record_deployment" * before "deploy:rollback", "trac:record_rollback" Order is important, otherwise the tasks will be looking at the wrong revisions. To manually record changes, simply run the record_deployment task to document the most recent deployment changes, or the record_rollback task to document a rollback that is about to be run. == REQUIREMENTS: * capistrano >= 2.0.0 * mechanize >= 0.6.10 == INSTALL: * sudo gem install capistrano_trac == LICENSE: (The MIT License) Copyright © 2007 FIX Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
gem install CapistranoTrac
for this version
gem 'CapistranoTrac', '~> 0.5.0'
October 3, 2007