You can stop an in-progress build by one of three methods:
-
Press Ctrl-C from the terminal where you invoked eMake
-
Use CloudBees Build Acceleration’s web interface
-
Use
cmtool— CloudBees Build Acceleration’s command-line tool
The Cluster Manager automatically terminates builds that seem to be hung. If the Cluster Manager does not receive a request from eMake for 60 seconds, it considers the build hung and the build is terminated.
Stopping a single build from the CloudBees Build Acceleration web interface
-
Click the Builds tab.
-
Click Stop Build in the Action column on the row exhibiting your build ID and Name.
Stopping multiple builds from the web interface
-
Click the Builds tab.
-
Go to the Filter drop-down menu and select the desired filter.
-
Click Run Filter.
-
Click Stop Filtered Builds.
-
From the Filter menu, select none, then click Run Filter.
Stopping a build using cmtool
| This is an advanced option for those who are familiar with using command-line tools. |
-
Request a list of running builds. The syntax is:
% cmtool --cm <clustermanager:port> getBuilds --filter <field name>=<value>For example, if linuxbuilder is the Cluster Manager host name, type:% cmtool --cm linuxbuilder getBuilds --filter "result =1"A list of running builds will display accompanied by a number of attributes for each build-for example: Build ID, machine name, build class, owner, build start time, and so on. The Build ID is used to identify a build for termination. Also, you can obtain additional information or include comments about the build. For example, to sort builds by start time and request only the first ten builds display, enter:% cmtool --cm linuxbuilder getBuilds --order Id --filter="ID<11"To get failed builds:% cmtool --cm linuxbuilder getBuilds --order "start_time desc" --filter "result >0" -
After you determine which build you need to terminate, use this syntax for ending a build:
% cmtool --cm <clustermanager> stopBuild <buildId>For example, to end build 4458, type:
% cmtool --cm linuxbuilder stopBuild 4458