The REVISION file is intended to be read-only, and so Capistrano itself
does not have any built-in mechanism for modifying it. You'll need to
write the tasks to do that yourself.
- Jamis
On 3/17/09 10:51 AM, Ian Sheridan wrote:
> I understand the that this breaks Cap revisioning but it does not
> break SVN revisioning, which is much more important to us. We moved
> from a rsync shell script to Cap and we like Cap much better as we
> have mroe Ruby coders then shell script gurus. So for small updates to
> the site we do a svn up and for larger full release updates we do a
> normal "cap deploy".
>
> Be that as is may, I am still looking to update the REVISION file
> without reinventing the wheel so to speak.
>
> - Ian
>
>
> On Tue, Mar 17, 2009 at 12:25 PM, Lee Hambley <lee.hamb...@gmail.com> wrote:
>> Ian,
>> You know of course that the svn-up mantra breaks the benefit of revisioned
>> releases with Capistrano, might I suggest you speed up an actual deploy with
>> deploy_via(:remote_cache)?
>> - Lee
>>
>> 2009/3/17 Ian Sheridan <ian.sheri...@gmail.com>
>>> Let me say what I am doing to place this in context. I am sending a
>>> list of files to a cache control system that we use, so that the files
>>> are either added or updated. To do this I need an Array of URIs. We
>>> use SVN and I make the array by parsing out the file names from "svn
>>> log -vq". This is the easy part already coded and working. The dilemma
>>> that I am encountering is that I NEED the REVISION file to match the
>>> working copy version. We have another task that is being used to just
>>> do a simple "svn up" on the current release. Previous to this caching
>>> need, we did not worry about the REVISION file. But now, I need to
>>> reset the REVISION file so that I can "svn log -vq
>>> -r#{current_revision}:HEAD" properly.
>>>
>>> Is there a command that I can run native to Cap to update this
>>> REVISION file? I have looked all over the code base and I am just not
>>> groking it. Can someone point me in the right direction? I could just
>>> do it myself, but if Cap is doing it already, why not use that
>>> instead?
>>>
>>> - Ian
>>>
>>> --
>>> ----------------------
>>> Ian Sheridan
>>> http://iansheridan.dyndns.org
>>> ----------------------
>>>
>>>
>>
>
>
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
capistrano-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
