1 comment
Comment actions Permalink

Hi Dejan,

The short answer is "no", at least not entirely.

TeamCity is a Java application and any plugin should have a JVM-running part using Java-exposed API.
That does not necessarily means Java, any JVM-trageted language with Java interoperability can be used for plugin writing. However, TeamCity plugin writing is not 100% documented experience and adding more variavbles to the mix can make the things quite complex,

When it goes about a build runner, one can get an existing plugin as an example to reuse the Java part and then make it invoke .Net executable on agent which will do the build running/reporting work in .NET. An example of such a plugin example can be FxCop.

Update: one more way to write a runner for TeamCity is to base it onthe exisitng runners: check meta-runner approach.


Please sign in to leave a comment.