Does TeamCity support GridGain?

See http://www.gridgain.com/product_junits.html

Basically this is a product to distribute running of JUnit tests on a grid of nodes. These nodes can be on the same computer as the build plus ones on the network. Using this distribution we can get our unit tests times down dramatically, but will it work with TC?

Importantly, how does TC monitor JUnit output?

4 comments

Basically this is a product to distribute running of JUnit tests on a grid of nodes.


Its that and so much more! Gridgain is a great and very easy to use product!

Have you thought about a custom ANT task to implement your Gridified distribution of tests? This way, you could do something like instead of ]]> and get the benefits of TC and GridGain.

0

Hello,

Currently, there is no support for GridGain in TeamCity. We are thinking about it, but I am not sure how soon this can turn into something working or something released.

I guess you can try running your tests with the GridGain and TeamCity knowing nothing about it. However, there might be issues with tests reporting.

Importantly, how does TC monitor JUnit output?

TeamCity pushes it's listener to the JUnit and reports the messages via age to the server.

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

On Fri, 01 Feb 2008 11:19:16 -0200, Yegor Yarko (JetBrains)
<no_reply@jetbrains.com> wrote:

Hello,

>

Currently, there is no support for GridGain in TeamCity. We are thinking
about it, but I am not sure how soon this can turn into something
working or something released.

>
I've said it before, something that seem easy to implement (ha!) is the
distribution of tests to agents. A naive implementation would start n
builds, and run t/n tests on each, and consolidate the results in a single
result. It has the benefit of working for every platform and runner, the
downside of multiple compilations of the same code...

Is that a crazy thing to ask?

Regards,
Pablo

--


Victory goes to the player who makes the next-to-last mistake.
-- Chessmaster Savielly Grigorievitch Tartakower (1887-1956)

Pablo Montilla
www.odyssey.com.uy

0

The problem with mulitple builds is that there will be multiple builds reported. We don't want16 builds saying that they have completed we just want 1. TC has no "consolidation" of builds - when a build is done it reports that it is done. Furthermore, what do you do about code coverage?

0

Please sign in to leave a comment.