Build can be forcibly stopped by clicking the stop button as below:
!stop1.png!
To stop multiple builds, please login as administrator and switch to _queues_ tab
!stop2.png!
{warning:title=Known Issue}When stopping a build, QuickBuild currently relies on JVM's process facility to kill the spawned build process (by calling _Process.destroy_). However this mechanism has a big limitation that it only kills the direct spawned build process. Any spawned child processes of the build process will still be running. For example, if the build script invokes a batch (or shell script) file, and the batch file calls _javac_ to compile the code, stopping the build only terminates executing of the batch process while leaving _javac_ process intacted. In this case, you will need to manually kill any spawned child processes. In the same time, we are investigating other approaches to work around this issue.{warning}
!stop1.png!
To stop multiple builds, please login as administrator and switch to _queues_ tab
!stop2.png!
{warning:title=Known Issue}When stopping a build, QuickBuild currently relies on JVM's process facility to kill the spawned build process (by calling _Process.destroy_). However this mechanism has a big limitation that it only kills the direct spawned build process. Any spawned child processes of the build process will still be running. For example, if the build script invokes a batch (or shell script) file, and the batch file calls _javac_ to compile the code, stopping the build only terminates executing of the batch process while leaving _javac_ process intacted. In this case, you will need to manually kill any spawned child processes. In the same time, we are investigating other approaches to work around this issue.{warning}