Subversion: working copy

All of our NAnt scripts require a Subversion working copy directory (you know, the ones with hidden the .svn directories). The reason is that the subwcrev utillity is used to put the revision number into a temporary copy of the AssemblyInfo.cs source file before compilation.

So, is there a way to force TC to create a "true" working copy? If not, is that a feature you're going to implement in the near term?

I've found a thread (dated from August 2006) describing a rather ugly work-around. If I got the basic idea right, the actual check-out is done by an additional script. I've some questions regarding this approach:

1. Does TC still have to monitor the Subversion repository? Is it possible to omit just the check-out process?
2. Where should I place the script? In a fixed path?
3. How do I pass the script the actual working directory? I mean where should it create the working copy?
4. Is it possible to share the same working copy between different build configuration?

Regards, Christian

3 comments

Another work-around that come to my mind:

Is it possible to pass the Subversion repository revision to the build scripts by command line parameters? If that's possible I could simply skip querying the revision and take the passed one instead.

Regards, Christian

0

Hello,

Hello,

I think you just need to select "checkout on agent" mode in build
configuration VCS settings. In this case a true update is performed on
agent.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Christian Schwarz" <c.schwarz@systemtechnik-online.de> wrote in message
news:31219015.1197575060945.JavaMail.itn@is.intellij.net...

All of our NAnt scripts require a true Subversion working copy directory
(you know, the ones with hidden the .svn directories). The reason is that
the subwcrev utillity is used to put the revision number into a temporary
copy of the AssemblyInfo.cs source file before compilation.

>

So, is there a way to force TC to create a true working copy? If not, is
that a feature you're going to implement in the near term?

>

I've found a thread (dated from August 2006) describing a rather ugly
work-around. If I got the basic idea right, the actual check-out is done
by an additional script. I've some question regarding this approach:

>

1. Does TC still have to monitor the Subversion repository? Is it possible
to omit just the check-out process?
2. Where should I place the script? In a fixed path?
3. How do I pass the script the actual working directory? I mean where
should it create the working copy?
4. Is it possible to share the same working copy between different build
configuration?

>

Regards, Christian



0

Thanks, that seems to work!

Christian

0

Please sign in to leave a comment.