- Type:
- Bug
- Priority:
-
Critical
- State:
- Fixed
- Subsystem:
- Server
- Reporter:
- Yegor Yarko (yaegor)
- Assignee:
- Olesya Smirnova (lesya)
- Affects:
- No affected versions
- Fixed in:
- Benares EAP (5930)
- Created:
- 17 months ago (13 Jun 2007 21:01)
- Updated:
- 9 months ago (25 Jan 2008 11:34)
- Votes:
- 0
- Resolved:
- —
- JIRA source:
- TW-2824
- Build:
- 5200
No attachments
Consider a CVS VCS root:
module: doubleAliasModule
CVS root: :pserver:admin@yavm-xp-bSrv:/Main
Where CVS module file has:
doubleAliasModule -a testdir1 testdir2
Agent checkout produces the structure:
<files from testdir1>
While Server checkout produces (correct) structure:
testdir1
<files from testdir1>
testdir2
<files from testdir2>
Issue wasclosed
| Old | New | |
| Yegor Yarko (yaegor) - 9 months ago (25 Jan 2008 11:34) | ||
Chad Loder (chadloder)
9 months ago (24 Jan 2008 03:15)Olesya,
I think I am still experiencing this problem with TeamCity 3.0.1 (build 6010). I am using ampersand modules with CVS and the structure that TeamCity produces when it checks out the sources is flat (the ampersand modules names should be used as directory names with the files under them).
Here is what I have as my CVSROOT/modules file:
{noformat}
productv4 &tools &src &doc &qa
tools tools
src src
doc doc
qa qa
{noformat}
Here is the expected (CORRECT) directory structure created by CVS:
{noformat}
tools/
doc/
src/
{noformat}
Here is the actual (INCORRECT) directory structure created by the built-in default agent with my new fresh install of TeamCity:
{noformat}
admin/
api/
build/
internal/
run/
shared/
{noformat}
Yegor Yarko (yaegor)
9 months ago (24 Jan 2008 12:52)Chad,
This seems like TW-3904. Could you please try to use agent checkout?
Chad Loder (chadloder)
9 months ago (25 Jan 2008 01:52)Yes, my issue is identical to TW-3904. I tried this with agent checkout and the correct structure was created.