Thanks but that doesn't really work in our situation. This is for ASP.NET
websites that require a build prior to pushing. Additionally we don't want
every commit to ever be pushed automatically.
Essentially what I'm hoping to have is create a tag from the trunk for the
build, say 1.1.0.12, build my assemblies and then have a third party script
(nant, ruby, etc) that determines exactly which files (binaries excluded)
that have changed, at the same time ignoring non web files such as .cs,
.resx, etc.
The next time I have to make a build I'd create a new tag (1.1.0.13) and
compare the files that changed between the tags and repeat the process
above.
Thanks.
Kyle Heon
kheon@comcast.net
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2005@ryandesign.com]
Sent: Wednesday, August 03, 2005 8:47 PM
To: kheon@comcast.net
Cc: users@subversion.tigris.org
Subject: Re: Getting list of files that changed between revisions
On 04.08.2005, at 02:31, Kyle Heon wrote:
> For our website build process what I would like to be able to do is
> create a deployment package that includes just the files that have
> changed since the last build to staging/live.
>
> What is the easiest way via Subversion to get a list of all changed
> files between a revision?
I feel that the best thing is not to do it that way.
Here's a description of how we handle our web site deployment:
http://svn.haxx.se/users/archive-2005-06/1754.shtml
I intended to condense that a bit and make it into a FAQ, but haven't
gotten around to it yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 4 03:04:37 2005