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

Ignore scenario - guidance appreciated.

From: Foster, Richard - PAL <RFoster_at_quixotecorp.com>
Date: 2005-03-28 17:09:28 CEST

Greetings all,

I have looked through the archives for this mailing list, and I am still
confused about how (or if) certain files in my source repository should
be handled.

The scenario is as follows:

* We run a continuous integration process. Changes in the source
code (as reported by Subversion) trigger the build.
* The build script (among other things) updates AssemblyInfo.cs
files. (Yup, it's a C# / .NET project).
* If the AssemblyInfo.cs files are not in the repository, then it
is not possible for a developer with *just* Visual Studio and Subversion
to get the source and build the project.
* If the AssemblyInfo.cs files are in the repository, then a
developer running the build script runs the risk of checking in an
updated file. This could cause a problem since it may result in a file
built on a developers machine appear to have been built as part of a
release build, or the continuous integration process (the build machine
is, alas, occasionally used by visiting engineers as a development

What is the recommended way of dealing with this scenario? Ideally, I
would like to be able to have the AssemblyInfo.cs files in the
repository, but not have Subversion complain or update them if they are
different on a developer's machine (unless explicitly asked to do so).
From what I have read, I do not believe Subversion would allow me to
accomplish this. Do I understand correctly, or have I missed something?

Received on Mon Mar 28 17:13:05 2005

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.