Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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:

  • This command is not useful for Single-Use VMs, which are launched for a one-time execution of build, and once the execution is completed, are terminated.  

  • To use the --avoid command with Android, you need to activate ccache using the following cchace command:
    env CCACHE_EXEC=/usr/bin/ccache USE_CCACHE=yes

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 --avoid command is OFF. When it is used, it applies only to the current build.

For example:

ib_console --avoid make -j 40

  • To verify the current size of the ccache, enter:

    CCACHE_DIR=/etc/incredibuild/cache/build_avoid/ubuntu.1000/ /opt/incredibuild/bin/ccache -s

  • To increase the size of the ccache, enter:

    CCACHE_DIR=/etc/incredibuild/cache/build_avoid/ubuntu.1000/ /opt/incredibuild/bin/ccache -M <size in GB>

--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 -d1 command during the re-executing of the build.

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:

ib_console -c Test make –j 40

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.     

  • -f - Give priority to remote distribution. This command instructs everything in the build that is indicated as "allow_remote" to run on remote machines. However, if no remote machine is available, the processes will run on the local machine. 

  • -f1 - The same as -f

  • -f2 - Force remote distribution. This command instructs everything in the build that is indicated as "allow_remote" to run on remote machines. If no remote machine is available, the processes will not run on the local machine, but will be in a pending state until a remote machine will be available.

    Note: If you are using the -f2 command and no remote machine is available, no progress will be shown in the bottom pane of the Build Progress screen. However, in the upper pane, the System Graphs, some activity may be registered since it reflects the processes that occur on the Initiator machine:

-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:

man 2 nice

--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 --no-monitor option can improve the build performance, but you should use it only if you do not need to save the build data and you do not want to monitor its progress.

For example:

ib_console --no-monitor make –j 40

  • No labels