[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Doing builds with subversion

From: Jim Sokoloff <jim_at_sokoloff.com>
Date: 2007-05-29 00:42:27 CEST

On Mon, 28 May 2007, Tom Kielty wrote:

> The first one deals with the tagging process for a build/release.

Consider always branching for a release. Branch (svn copy) as
the first step, then checkout that working copy. If it builds,
great. If it doesn't, the developer responsible checks their
fix into mainline and svn merges that into the branch and
also commits it there. You then re-spin the build by doing
an update on the build machine (which is "looking at" the
branch, which only has that one change) and continuing.

> The next issue deals with updating files during the build.
> So my question is am I stuck not updating the files to prevent the 100
> revisions, or is there a way to do a commit on only certain files and
> ignore the rest?
> i.e. svn ci *.rc -m"Updated per the build"

That would work on Unix shells as they expand the arguments before
running the svn command. Doesn't work in cmd, as cmd doesn't work
that way.

However, you can use a response file with the --targets command,
so you can

dir /b *.rc > files.lst
svn ci -m "Updated by the build" --targets files.lst


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 29 00:43:41 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.