Votes

Share

Usually, when build is stopped, stop command is sent to the build agent. On build agent, some native code is involved to kill all processes spawned by the build. If this killing was successful, appropriate message is sent to the server and build is considered successful and agent free to accept new builds.

If there is no "build is killed" feedback from agent, server unregisters this build agent. But this step occurs only after 5 minutes timeout since "Stop" button is pressed.

Stop build functionality should work reliably this way on Windows, Linux, and MacOSx. We'll try hard to support this reliably on other Unix platforms, but most likely, only in Calcutta (next big TeamCity release).

We have alike issue reported: http://jetbrains.net/tracker/issue/TW-4668We've done some steps to improve the stability of the feature, but the changes are not yet included in the 3.1.x branch. The behaviour still needs more investigation.

As Kir noted, agent logs should shed some light on the reason the agent is stopped.

We would appreciate if you can send us your agent logs (e.g. attaching to the issue or uploading to ftp://ftp.intellij.net/.uploads and letting us know the exact file name).

Can you also check what java processes are running after the build stopping (before you run the agent manually), what are their command lines?