Version 3.10.0

• Android Open Source Platform (AOSP) 11 is now supported.
• The installation and upgrade process are now both run from the same unified installer.
• The system requirements have been updated.
• We added a few new graphs and improved the way graphs are selected.
• You can now stop builds that are in the pending status.
• As always, each release also includes bug fixes and stability improvements.

Version 3.9.0

Incredibuild Linux UI now supports:

Filter-based Bulk operations on multiple machines in the Coordinator monitor

Coordinator monitor view - selecting optimal number of entries per page

Coordinator monitor view filter - added  dropdown for selecting the searched column

Bug fixes and stability improvements.

Version 3.8.3

Full release notes

Version 0.96.80 

New Support for Android 10 (Q) (AOSP)

IncrediBuild Linux now accelerates the execution of Android 10 (Q) builds.

For more information, see Executing Android 10 OS Builds.

Bug fixes and stability improvements.

Version 0.96.71

A New Type of License - Single-Use VM

IncrediBuild Linux now offers a new type of license – Single-Use VM (SUVM). This license is designed for Virtual Machines or containers that are launched for the sole purpose of providing additional CPU resources to a task execution. After the task for which they were launched is completed, these machines are terminated. A SUVM license is allocated automatically by the Coordinator to this kind of machines when they are up. Once the task ends and the machines are terminated, the SUVM licenses are automatically deallocated, and they return to the Coordinator for re-use with other machines. For more information, contact Sales@IncrediBuild.com. 

A New Build Avoidance Capability

A new built-in caching option is available, which accelerates the task execution process by not rebuilding objects that are up to date. This Build Avoidance capability can be easily enabled and disabled from the shell, according to changing needs and resources.

Bazel Support

IncrediBuild Linux now supports Bazel versions up to 0.25.0, and Bazel sandbox builds.

Additional Improvements:

• Installation improvements.
• Simplifying and securing the configuration process of the network ports, which are required for the operation of IncrediBuild Linux.

Version 0.96.37

Miscellaneous

• Solved an issue that could cause builds to fail during an IncrediBuild Coordinator restart.
• Solved an issue that would cause a running build to fail if the Initiator would lose a connection with the IncrediBuild Coordinator.
• Various stability improvements.

Version 0.96.26

Build Systems support:

• IncrediBuild now offers experimental support for speeding up Gradle builds. For additional information please contact us at support@incredibuild.com

Performance

• A new option that improves execution performance by up to additional ~20% was added to the product. This option disables the ability to view data collected by IncrediBuild that is used for displaying the IncrediBuild graphical build monitor and used for the build queries. Console window build output and build history information is still available when this option is used. There are two ways to use this option:
  • Add the --no-monitor flag to the ib_console command line.
  • In the initiating machine's Agent Setting, disable the "Enable Build Monitor" check box under the Visualization tab:

Image Modified

• Some general performance optimizations may increase performance by up to additional 7%. 

Miscellaneous

• IncrediBuild now maintains the license core allocation across Agents when a new license is loaded to the Coordinator.
• Various stability bug fixes

Version 0.95.12

Build Systems support:

• IncrediBuild now offers experimental support for the Bazel build system. A benchmark for compiling the popular TensorFlow project showed a x7.5 acceleration boost, bringing TensorFlow compilation from 65 minutes down to 8.5 minutes.

• To run Bazel builds with IncrediBuild the following should be added to the regular Bazel command:

  Info
  --jobs=N --local_resources=R,N,1

  where N is the total number of cores on and your IncrediBuild infrastructure while the R parameter should be N*200, i.e. if there are 70 cores on your IncrediBuild infrastructure, the command should be:

  Info
  --jobs=70 --local_resources=14000,70,1

  
  

• ccache support: IncrediBuild now fully supports ccache in all operating modes (explicit invocation and implicit via soft link) - see ccache manual for details https://ccache.samba.org/manual.html#_run_modes 

   ccache database created while using IncrediBuild might be used by builds that are executed without IncrediBuild and vise-versa, i.e. there is a full interoperability of ccache regardless of IncrediBuild invocation.

Installation:

• In order to avoid trouble during IncrediBuild version upgrade on the customer side, a new utility script is introduced: ib_apply_upgrade.sh (resides in /opt/incredibuild/management). This script should be executed with sudo on the machine where the Coordinator is installed and receives a single parameter – the upgrade tar file. Example command line:

  Info
  sudo /opt/incredibuild/management/ib_apply_upgrade.sh incredibuild_upgrade_0.94.95.tar.bz2

  This way it will be properly extracted to the correct location, and the Coordinator then updates all of the agents on the network to its own version.

• Changes in the IncrediBuild n installation:

  -O <coordinator ip/hostname> now is required only when -C option is not given. When installing the coordinator, it should always use the localhost, therefore -O is not required and even ineligible in this case.

Miscellaneous:

• chroot management scripts were updated to correctly support schroot:

  Now there are two scripts: ib_chroot.sh and ib_schroot.sh

  ib_chroot.sh is for regular chroots – the syntax remained the same.

  ib_schroot.sh is for schroot users. The main difference is that ib_schroot.sh expects a name of chroot as a parameter instead of a directory where chroot is created. This complies with the regular syntax of schroot. Add and remove semantics are the same and are displayed in the command line help.

  
  

  Important: In order to make schroot directories be accessible by IncrediBuild, the following line should be added to the file /etc/schroot/default/fstab  

  Info
  /opt/incredibuild /opt/incredibuild none ro,bind 0 0