5 vcs roots enter, 1 vcs root leaves

Hello Scott,

Just to be sure that the other VCS roots produce something would you please
temprorarily detach the last VCS root, launch a build, and see if there're
some of the files that you expect to see in the checkour directory.

Thank you.

Hopefully someone can share with me what I'm doing wrong.

I've got a build configuration with 5 vcs roots. Each root is
connected to a Starteam view (not my choice!) and checking out from a
promotion state. When the build runs, the artifacts from last defined
VCS root checked are the only ones in the checkout directory.

What I want is to have N VCS roots under one configuration checkout
all their artificats into one directory. For this configuration it's
the sum of the parts that matter.

Here is the build log.

: Checking for changes
: Clearing temporary directory:
/usr/local/teamcity/buildAgent4/temp/buildTmp
: Checkout directory:
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
: Updating sources (10s)
: Will perform clean checkout
: Clean checkout reasons
: Checkout directory is empty or
doesn't exist
: "Clean all files before build"
turned on
: Agent doesn't have any version of
the project sources
: Building clean patch for VCS root:
XXXX[Pre-Production]
: Building clean patch for VCS root:
YYYY[Pre-Production]
: Repository sources transferred: 1.99Mb
total
: Removing
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
: Removing
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
: Removing
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
: Updating
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
: Removing
/usr/local/teamcity/buildAgent4/work/305bbc268b9627f2
---
Original message URL:
http://www.jetbrains.net/devnet/message/5240773#5240773

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

Well, I tried a number of configurations and the result was always the same.  The only artifacts left in the checkout dir after the checkout is done are the artifacts from the last vcs root in the list.

Interestingly, I was talking with a co-worker this monring and he is using multiple VCS roots on a different project but they are attached to CVS.  So maybe this is something specific to the StarTeam VCS root?

This is really a big issue for us.  We literally will have hundreds of vcs roots (~30 views with ~15 promotion states per project).  If we have to define a seperate build configuration for each one, well, it's going to be nasty ...

Hello Scott,

This potentially could be specific to the StarTeam plugin. I'll check this
locally.
Thank you for the information.

Well, I tried a number of configurations and the result was always the
same. The only artifacts left in the checkout dir after the checkout
is done are the artifacts from the last vcs root in the list.

Interestingly, I was talking with a co-worker this monring and he is
using multiple VCS roots on a different project but they are attached
to CVS. So maybe this is something specific to the StarTeam VCS root?

This is really a big issue for us. We literally will have hundreds of
vcs roots (~30 views with ~15 promotion states per project). If we
have to define a seperate build configuration for each one, well, it's
going to be nasty ...

---
Original message URL:
http://www.jetbrains.net/devnet/message/5240780#5240780

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

Hello Scott,

I seem to have found the problem. Can I send you the patch so that you could
check?

Well, I tried a number of configurations and the result was always the
same. The only artifacts left in the checkout dir after the checkout
is done are the artifacts from the last vcs root in the list.

Interestingly, I was talking with a co-worker this monring and he is
using multiple VCS roots on a different project but they are attached
to CVS. So maybe this is something specific to the StarTeam VCS root?

This is really a big issue for us. We literally will have hundreds of
vcs roots (~30 views with ~15 promotion states per project). If we
have to define a seperate build configuration for each one, well, it's
going to be nasty ...

---
Original message URL:
http://www.jetbrains.net/devnet/message/5240780#5240780

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

Yes.  How would you like to send it to me?

I prefer email :)
Please send a message to teamcity-feedback@jetbrains.com and I'll reply.

Thank you!

Yes. How would you like to send it to me?

---
Original message URL:
http://www.jetbrains.net/devnet/message/5240790#5240790

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

Hello Scott,

Have you received my email? Does it help?

Yes. How would you like to send it to me?

---
Original message URL:
http://www.jetbrains.net/devnet/message/5240790#5240790

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

I'm seeing this exact behavior in TeamCity 4.5.4, but I'm using two SVN roots.

Was the issue you addressed specific to his VCS or to TeamCity?

Also multiple VCS roots works when it is set to checkout on server, it's only when I set it to checkout on agent (which I need to be able to commit back to SVN) that it breaks.

Thanks,
Josh