The following table lists the optional execution commands for IncrediBuild Linux:
Note: To display the help for the execution commands of IncrediBuild Linux, enter the -h
or --help
parameter after the ib_console
command:
ib_console -h
Execution Command | Description |
--avoid | Avoid re-building objects that are up-to-date in order to accelerate the build execution and improve performance. This Build Avoidance command reduces the build time by using a built-in caching option, which enables you to rebuild only objects that were modified, and not the whole code base. The performance improvement will be mainly manifested from the second execution onward, after the cache is populated in the first build execution. Notes:
Using this command requires additional storage space, which is allocated on the Initiator machine for the cache. It is recommended to allocate for this cache 15 GB. By default, the For example:
|
--ib-crash | For log export: if a build crashes, and you want to export its log and send it to IncrediBuild Support, this command adds information to the log that can help discover the causes of the crash. This command should be used together with the Using this command may impact the build performance. For more information, see Using the --ib-crash Command. |
-c / --caption | Specify a build name in order to display it in the Build Caption column of the Build History. This command is for display purposes only. For example:
Note: If you are entering more than one word as the build caption, do not use a blank space between the words. |
-d1 | For log export: if a build hangs or gets stuck during execution, or if a build fails with error messages and you want to export its log, this command adds important information to the log. This command should be used during the re-executing of the build. For more information, see Using the -d1 Command. |
-f, -f1, -f2 | For managing the execution of processes that are defined as "allow_remote" in the ib_profile.xml file.
|
-n | Specify a Nice value to set the priority of the process. A Nice value should be numeric and between -20 (high priority) and 19 (low priority). To learn more about Nice, enter:
|
--no-monitor | Do not save the build data in the database. The build record will appear on the Build History, but its data will not be displayed in the Build Progress for monitoring. Note: Using the For example:
|