Our test process involves:
1) Building an ear
2) Deploying an ear to jboss app server
3) Starting app server
4) Run tests
5) Shutdown jboss
I think this is a pretty common use case. Occasionally as we develop, me mess things up so that JBoss does not correctly startup. A side effect of that is that we do not shut it down correctly.
When the next build on that agent happens, jboss is still "running" and holding onto some ports causing the subsequent runs to fail.
We currently handle this in our build scripts with os specific (<exec cmd="kill" for windows and shell script on unix side) commands.
In looking through the open api i can see some classes related to process management.
Is it possible to leverage Teamcity openapi in order to manage these processes via a plugin?
For example, if I wrote an agent plugin and listened on a build finished, is there a mechansim for killing any created processes? If so, can you point me in the right direction?