Distributed resources

I'm a newbie to this forum/TeamCity and have a basic question.
We want to convert our CruiseControl project to something like TeamCity. But we would like to be able to distribute the load of the build across multiple machines. For example, when running a suite of unit tests, it could use multiple machines in parallel to do this. This would be a big savings in build time.
I've looked at all the doc/FAQs and I see that you can distribute builds across machines. Therefore we could split up our build into smaller pieces but this becomes a management nightmare. All we want to do is have a build script and let the builder figure out how to distribute all the processes to multiple machines. Does TeamCity have this capability?

2 comments
Comment actions Permalink

JT Keller wrote:

I'm a newbie to this forum/TeamCity and have a basic question.
We want to convert our CruiseControl project to something like TeamCity. But we would like to be able to distribute the load of the build across multiple machines. For example, when running a suite of unit tests, it could use multiple machines in parallel to do this. This would be a big savings in build time.
I've looked at all the doc/FAQs and I see that you can distribute builds across machines. Therefore we could split up our build into smaller pieces but this becomes a management nightmare. All we want to do is have a build script and let the builder figure out how to distribute all the processes to multiple machines. Does TeamCity have this capability?


We definelely have plans to support your scenario, but this feature
won't be available in TeamCity 1.0.

May I ask you, what is duration of your builds? tests?

With kind regards,
KIR

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

0
Comment actions Permalink

Our regular builds with unit tests take over 6 hours to complete. Our night build which has more tests and code coverage reports take 14 hours to complete. Plus as any good development team should do ;) - we will be adding more and more time consuming tests as we move forward.

The build (compiling, javadocing, etc) takes about 20 minutes of this time.

0

Please sign in to leave a comment.