No Subversion compatible working copy -> problem

Teamware doesn't create a Subversion compatible working copy when checking out files vom Subversion. The .svn directories are missing.

I'm having problems with this, because my builds use different svn commands which don't work anymore. For instance, I call subwcrev from TortoiseSVN to get the revision number of the working copy. The revision number is used as a version number inside the code.

What can I do?

Ingo.

4 comments
Comment actions Permalink

Hi Ingo

I ran into this issue also as I need to commit versioning changes in some of my builds.

To get round it, you need to stop the build agent from accessing the vcn and then perform the checkout from within your build script (I'm using ant macros hooked up to javasvn or the cvs task).

It would be good if the Build Agent was able to perform the checkout/update and maintain the working copy. Is this possible?

hth

-Paul

0
Comment actions Permalink

Disable 'checkout on server' property for the configuration and perform
checkout activities from your build script.


"Ingo Adler" <ingo.adler@synacon.ch> wrote in message
news:5094669.1154786396261.JavaMail.itn@is.intellij.net...

Teamware doesn't create a Subversion compatible working copy when checking
out files vom Subversion. The .svn directories are missing.

>

I'm having problems with this, because my builds use different svn
commands which don't work anymore. For instance, I call subwcrev from
TortoiseSVN to get the revision number of the working copy. The revision
number is used as a version number inside the code.

>

What can I do?

>

Ingo.



0
Comment actions Permalink

The build script is in the subversion repository too.

How do I get the newest version from Subversion to the place where TeamWare needs it (except copying it there manually)?

What's the reason, that you don't create a real Subversion working copy when you checkout or update the sources?

Disable 'checkout on server' property for the
configuration and perform
checkout activities from your build script.

>

0
Comment actions Permalink

The build script is in the subversion repository too.

>

How do I get the newest version from Subversion to the place where
TeamWare needs it (except copying it there manually)?


Define build file content instead of path to build file. Using thins
bootstrap script you can checkout svn sources into the working directory

What's the reason, that you don't create a real Subversion working copy
when you checkout or update the sources?

Actually, server doesn't perform svn checkout, so there are no svn admin
files to be sent to an agent

"Ingo Adler" <ingo.adler@synacon.ch> wrote in message
news:15491687.1155065123676.JavaMail.itn@is.intellij.net...

The build script is in the subversion repository too.

>

How do I get the newest version from Subversion to the place where
TeamWare needs it (except copying it there manually)?

>

What's the reason, that you don't create a real Subversion working copy
when you checkout or update the sources?

>
>> Disable 'checkout on server' property for the
>> configuration and perform
>> checkout activities from your build script.
>>


0

Please sign in to leave a comment.