CVS update for a build does not create new directories

- we have a couple of builds where, upon building the project, newly created directories in CVS do not get checked out properly into the build
area - as if the cvs up command was issued rather than cvs up -d. This does not seem to happen across all projects, so I'm not
sure whether we've just not noticed this behaviour on these other projects. In any case, is there any way to control this without resorting to using
clean checkout every time we build?

Cheers,

Bonny

3 comments

What checkout type do you use in these build configurations? Could you please check that time is synchronized between TeamCity server and CVS repository?

--
Pavel Sher

0

Pavel,
The checkout on all of our projects is done on the the agent (which happens to be on the same box as the server which is also the CVS server).
This is not a question of timing IMO, since new Java files are being detected and added to the build OK, it's just these
directories that are empty (part of our build procedure requires them like that) that do not get created.

Any log I could look in to find out the mode in which the agent does the update? the main log is full of the TC server update messages, but there's
no raw CVS messages anywhere (ie. like in IDEA where one can see the actual CVS output), so is there a way to turn such a facility on?

Cheers,

Bonny

0

It seems we need an option in VCS root settings telling us whether to remove empty directories or not. Currently they are always removed (event when clean checkout is performed). Please watch/vote for this issue: http://jetbrains.net/tracker/issue/TW-5708

Currently to workaround a problem you probably can put files into these directories and remove them when build script starts.

--
Pavel Sher

0

Please sign in to leave a comment.