Version History

This section lists changes introduced in all released IncrediBuild versions:

Contents:

Changes in Version 9.3.5

Changes in Version 9.3.5 (Release Date: December 6, 2018)

Version Highlights

  • This version of IncrediBuild provides experimental support for Visual Studio 2019.

FreeDev

  • Fixed an issue where some of the FreeDev agents would become “Expired” prior to the allowed 30-day limit.

Visual Studio

  • IncrediBuild’s predictive execution for optimized compilation performance certifies MSBuild version up to:
    • 15.9.20.62856 for Visual Studio 2017;
    • 16.0.218.25180 for Visual Studio 2019 Preview.
  • Fixed a rare scenario when building an Xbox project within Visual Studio could produce the following error:
    error MSB6003: The specified task executable “X” could not be run. The process cannot access the file ‘Y’ because it is being used by another process”.
  • Fixed an issue that would cause the /vsversion=vc15 switch to be ignored when only VS 2017 Build Tools are installed.

Miscellaneous

  • Added a warning when the /profile command line switch points to a profile that cannot be found.

Antiviruses

  • Stability fixes for issues that could occur when using IncrediBuild on machines with “Avecto Privilege Guard” and “Trend Micro” Security software.
Changes in Version 9.3.3

Changes in Version 9.3.3 (Release Date: November 7, 2018)

IncrediBuild for test acceleration (NUnit, GTest, VSTest, xUnit, and others)

Are you being held back by time-consuming test executions? Wait no more!

Become more agile by accelerating your test executions using your existing IncrediBuild infrastructure both on your continuous integration as well as shift-left to allow developers and testers to execute tests much much faster.

Contact us at [email protected] and become an early adopter for the new IncrediBuild test acceleration capabilities.  

IncrediBuild Enterprise

  • Developers can now build in parallel from two different instances of Visual Studio IDE. IncrediBuild’s distribution capabilities will serve both IDE builds in parallel, highly accelerating both builds while optimizing the IncrediBuild infrastructure utilization.
  • Dashboard performance improvement for querying a very large dataset.
  • You can now configure the cost-per-hour field with which IncrediBuild calculates the estimated “costs saved” KPI.

Visual Studio

  • This version of IncrediBuild certifies Visual Studio version 15.8.9.
  • You can now upgrade your IncrediBuild version without needing to close the Visual Studio IDE.
  • Added support for IncrediBuild keyboard shortcuts in Visual Studio 2017
  • IncrediBuild’s predictive execution for optimized compilation performance certifies MSBuild version up to 15.8.169.51996.
  • IncrediBuild now supports the scenario in which users have two different minor versions of Visual Studio installed and the VCToolsVersion property file (such as: “Microsoft.VCToolsVersion.14.12.props”) contains a condition that specifies which version to use.
  • Fixed a problem that could occur when installing IncrediBuild using the silent install option IBSetupConsole /AGENT:INSTALLADDINS=ON with Visual Studio 2017.

Miscellaneous

  • The size of the IncrediBuild setup was reduced by 25% to only 60 megabytes.
  • Minor bug fixes.
Changes in Version 9.3.2

Changes in Version 9.3.2 (Release Date: October 3, 2018)

Version Highlights

This version of IncrediBuild certifies Visual Studio version 15.8.2

IncrediBuild’s predictive execution for optimized compilation performance certifies MSBuild version up to 15.8.168.64424

 

Improved support for distributing DirectX-related processes to remote machines

In this version of IncrediBuild, we’ve enhanced the IncrediBuild virtualization engine to cover many various aspects of the ability to remotely execute processes that are using DirectX. Many IncrediBuild users are highly accelerating home-grown and commercial graphic-related executions using the various IncrediBuild integration options.

 

Accelerate VSTest unit test executions (Beta)

This version of IncrediBuild introduces a beta feature for users with time-consuming VSTest executions, which allows to distribute and highly accelerate VSTest executions.

At this stage, only command-line VSTest executions are supported. If you are executing your VSTests using continuous integration tools or through the command line, please contact us at [email protected] and we’ll be glad to assist you with accelerating your test cycles.

Learn how NCR and ModuleWorks achieved better productivity and faster time-to-market by accelerating their test cycles with IncrediBuild.

 

Windows Core OS (Experimental)

Improved support for IncrediBuild Agents running within Windows Core OS hosts

 

Windows Docker Containers (Experimental)

Various fixes related to working with IncrediBuild within Windows Docker Containers

 

IncrediBuild Enterprise Edition

  • IncrediBuild extension for TeamCity (Experimental)

If you are using TeamCity for your continuous integration, we have some good news for you. With this new IncrediBuild extension for TeamCity, users can create and execute IncrediBuild build steps seamlessly from within TeamCity using a convenient standard TeamCity UX.

  • Added an option to manually reset a “Single-Use Virtual Machine” image in scenarios where users require to update the image from which they provision their VMs. The “Single-Use Virtual Machine Image” featureallows users to provision and de-provision virtual machines from an image. An IncrediBuild license allocated to these VMs will automatically be released by IncrediBuild back to the license pool once the VM is destroyed.
  • Various improvements to the IncrediBuild extension for Jenkins.
  • Various improvements and fixes to the IncrediBuild Enterprise Dashboard

Visual Studio & MSBuild

  • Improved performance for Cuda compilations and possibly other compilers in scenarios where the /e compiler switch (pre-processing) is being used as part of the compilation tasks.

IncrediBuild’s predictive execution considers compilation tasks with the /e flag as blocking other dependent tasks from being executed in a predictive, parallel manner. This may result in sequential execution of Cuda compilation tasks (which is the default behavior in Visual Studio). With this new feature, users can experiment whether performance can be improved by forcing the IncrediBuild predictive execution to operate in these scenarios. In order to achieve this behavior, a registry value should be created on the Initiator machine:

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Xoreax\IncrediBuild\Builder

String Value: AllowPredictedInPreprocessCL

Set this registry string value to “1” to enable predicted for CL tasks with /E parameter

  • The IncrediBuild build monitor was added to Visual Studio 2017 “View” menu option
  • Fixed an issue that could have led users building Visual Studio solutions with IncrediBuild under a service account to receive an error message saying: “MS Visual Studio xx.x is not installed on this computer” (usually in continuous integration tools such as Jenkins and others)
  • Fixed an issue that could have led IncrediBuild to omit the >1, >2, prefixes in Visual Studio and MSBuild output
  • Fixed some rare scenarios in which build success status wasn’t reported correctly
  • Various bug fixes

Miscellaneous

  • Fixed a rare scenario in which some Agents could become offline for short periods of time in very large IncrediBuild deployments
  • Various UX fixes and improvements

 

Changes in Version 9.3

Changes in Version 9.3 (Release Date: June 3, 2018)

Version Highlights

  • This version of IncrediBuild certifies Visual Studio version 15.7.2.
  • IncrediBuild’s predictive execution for optimized compilation performance certifies MSBuild version up to 15.7.179.6572.
  • IncrediBuild now supports the ability to build inside Continuous integration and Continuous delivery environments compiling Visual Studio projects in scenarios where only the Visual Studio build tools are installed on the build machines and not the Visual Studio IDE.

IncrediBuild Console Exit Code

  • IncrediBuild Console (BuildConsole and IBConsole commands) now exit with the exit code returned by the tool IncrediBuild executed.
  • Exit codes indicating IncrediBuild internal errors are now user-selectable in order to avoid clashes with build tools’ own exit codes.

Windows Core OS (Experimental)

  • IncrediBuild can now be used inside Windows Core OS (WCOS) as Initiator Agents. IncrediBuild Agents can be installed in a Windows Core OS and participate as Initiators. The IncrediBuild Agents operating as Helpers function inside Windows Core OS is coming soon.

Windows Docker Containers (Experimental)

  • IncrediBuild can now be installed and used as an Initiator inside a Windows Docker container environment. This allows IncrediBuild users to use IncrediBuild as part of Continuous Integration and Continuous Delivery workflows that are working with Windows Docker containers.
  • In scenarios where the Docker containers are constantly provisioned and de-provisioned, it is recommended to use IncrediBuild Enterprise Edition’s feature that automatically allocates a license to the IncrediBuild Agent installed inside the Docker container and automatically releases the license back to the IncrediBuild license pool once the Docker container is deleted.
  • Additional information about this feature can be found at the following link: https://incredibuild.atlassian.net/wiki/spaces/IN/pages/65538/Single-use+Virtual+Machine+Image.
  • In this version of IncrediBuild, Agents installed inside a Windows Docker container can only operate as Initiators and won’t operate as Helper instances.
  • The IncrediBuild Agents installed inside a Docker container to operate as Helpers functionality is coming soon.

Critical fix for Windows 10 build 17040

  • Already introduced in IncrediBuild version 9.22., this is a fix for a critical issue introduced in Windows 10 build 17040.
  • The issue was caused by a newly introduced Windows API that prevented tasks from executing on Helper machines running Windows 10 build 17040 and later.

Visual Studio

  • Users can now manually update the MSBuild version number that will be certified for IncrediBuild’s predictive execution for optimized compilation performance. For further information navigate to the following link:
    https://incredibuild.atlassian.net/wiki/spaces/IUM/pages/39452740/Predictive+Execution+and+MSBuild+Versions.
  • Added the ability to reopen the IncrediBuild build monitor within Visual Studio 2017 using the Visual Studio “View” menu.
  • Fixed an issue that prevented IncrediBuild from compiling C# projects when the C++ workload wasn’t installed as part of the Visual Studio installation.
  • Fixed an issue that could have led the IncrediBuild for Visual Studio plugin to fail with “.NET Framework Initialization Error”.
  • Fixed an issue that could cause IncrediBuild to fail with “c1xx: fatal error C1083: Cannot open source file: [file name]” when compiling xaml generated cpp.
  • Fixed an issue that could have led IncrediBuild to fail with: “cl : Command line error D8037 : cannot create temporary il file; clean temp directory of old il files”.
  • Fixed a rare scenario that could have led IncrediBuild to mark the build’s status bar as succeeded, although the build failed.

Make and other Build Tools Solution

  • The Android NDK build tools are now fully supported as part of the IncrediBuild for Make and Other Build Tools solution. With this version of IncrediBuild, the following processes will be distributed automatically to Helper machines: arm-linux-androideabi-g++, arm-linux-androideabi-gcc, x86_64-linux-android-g++, x86_64-linux-android-gcc, aarch64-linux-android-g++ and aarch64-linux-android-gcc.
  • Certified support for Ruby version 2.4. Users can now accelerate Ruby builds by distributing Ruby compilations to remote machines using the IncrediBuild DevTools interface.
  • Certified support for the latest Xilinx compiler – arm-linux-gnueabihf-g++.exe

Miscellaneous

  • Fixed an Issue in the IncrediBuild integration with the Nintendo Switch platform that could have led IncrediBuild to build unnecessary files in a specific scenario.
  • The IncrediBuild Coordinator Monitor and the XLicProc command for loading a license through the command line now support elevated privileges.
  • Fixed an issue related to OfficeScan antivirus, which could have led IncrediBuild to fail with “Failed to load build set” on machines with this antivirus installed.
  • Fixed an issue that could have led IncrediBuild to fail with “ERROR: INSERT has more expressions than target columns” on operating systems with a few specific locales.
  • The build status bar will now be colored white for builds that were canceled by users instead of yellow. The yellow color will be used only for builds that failed with warnings.
  • Fixed a rare scenario that could have led IncrediBuild to fail with “THandleIntegerMap_HashTable: Hashtable does not allow duplicates”.
  • Fixed a rare scenario to could have led Agents to disconnect from the IncrediBuild Coordinator.

(Back to top)

Changes in Version 9.2

Changes in Version 9.2 (Release Date: December 24, 2017)

Version Highlights

  • This version of IncrediBuild is certified for all Windows operating systems with updates released up to the 7th of December 2017.
  • We’ve recently introduced a new extension for QTCreator. If you’d like to try it out, please contact us at[email protected].
  • Known issue: Please note that the Windows 10 Fall Creators Update (FCU) 1709 contains a bug that causes CreateWindow() and CreateWindowEx() to fail unpredictably. This is a known issue which affects many Visual Studio extensions and was acknowledged by Microsoft. For more updates from Microsoft and possible future fixes, please follow this link: https://support.microsoft.com/en-us/help/4054150/issues-when-windows-10-fall-creators-update-calls-createwindowex-for-s. This issue may cause the IncrediBuild extension for Visual Studio to crash intermittently.
  • Visual Studio: This version of IncrediBuild is fully certified for Visual Studio 2017 update 4 (version 15.4.4) along with the MSBuild version which was released with the update.
  • Visual Studio: Upgrading IncrediBuild through the Visual Studio setup will now upgrade the IncrediBuild product as well as the IncrediBuild extension for Visual Studio.
  • Visual Studio:Better handling of scenarios when IncrediBuild compiles solutions that execute using the Visual Basic compiler.
  • Make and Other Build Tools: The Arm compiler “arm-xilinx-linux-gnueabi-g++” is now supported by default as part of the IncrediBuild for Make & Build Tools solution.
  • Make and Other Build Tools: IncrediBuild will now make the jom build system better parallelize processes by default when executed using the IncrediBuild for Make & Build Tools solution.
  • Bug fixes: Fixed a bug that was introduced in version 9.0 when executing an MSBuild compilation using “buildconsole /command” that could result in IncrediBuild returning “xgTaskID=00000000” in the stderr stream of a compilation task which could potentially cause the compilation to fail.
  • Bug fixes: Various minor bug fixes.

(Back to top)

Changes in Version 9.01

Changes in Version 9.01 (Release Date: October 4, 2017)

Version Highlights

  • Fixed various issues.

(Back to top)

Changes in Version 9.00

Changes in Version 9.00 (Release Date: September 5, 2017)

Version Highlights

  • This version of IncrediBuild certifies all Windows operating system updates released up to the 18th of August 2017.
  • This version of IncrediBuild fully certifies Visual Studio 2017 update 3 along with the MSBuild version which was released with the Visual Studio 2017 update 3 version.
  • There are currently two known issues related to Visual Studio 2017 update 3:
    1. Supporting the Visual Studio “Lightweight solution loading” feature is yet under development and currently not supported.
    2. Changes made to Visual Studio 2017 update 3 prevent IncrediBuild’s Build Monitor -> Project View from showing the colored status of each project when compiling with this version of Visual Studio. We are working on fixing this issue in the next version of IncrediBuild.
  • As part of the IncrediBuild team’s effort of developing a new and optimized solution for highly accelerating C# code bases, we’ve added some improvements to our existing support for C# acceleration for solutions with more than 30 projects. In scenarios where multiple MSBuild solutions are executed in parallel, the new IncrediBuild feature for concurrent execution can provide a meaningful benefit for accelerating full C# build cycles.
  • As Nuget is gaining popularity, IncrediBuild is now capable of coping with scenarios where a build triggered from within Visual Studio is configured to restore missing Nuget packages. We are currently working on supporting this scenario as part of our out-of-the-box support for Visual Studio. In the current version, you’ll be required to create a registry value in order for IncrediBuild to cope with this scenario. In order to achieve this behavior, on the Initiator machine, create a registry string value named AutoRestoreNugetPackages under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Xoreax\IncrediBuild\Builder and set its value to 1.
  • IncrediBuild can now be used to accelerate builds executed by the popular QT Creator IDE. An IncrediBuild plugin for QT Creator is currently under development. For instructions on accelerating QT Creator builds, please contact us at
    [email protected]This email address is being protected from spambots. You need JavaScript enabled to view it.
  • IncrediBuild can now highly accelerate your CTest executions. CTest is a testing tool distributed as part of CMake. If you are interested in accelerating your CTest executions please contact us at
    [email protected]This email address is being protected from spambots. You need JavaScript enabled to view it.
    for further instructions.
  • Users can now Change the IncrediBuild buildconsole’s exit code by using “/IbExitCodeShift=” command line switch.
  • A new feature was added in IncrediBuild build monitor->progress view that allows users to search for a specific bar(s). Pressing “Ctrl+B” in the progress view areas will allow you to enter a text to be searched across the captions of the bars represented in the progress view. Once the “OK” button will be pressed, all the bars containing the search text will be highlighted and a text file will be created and opened in your default text editor program to show the list of tasks that apply to your searched text.
  • Users can now change the location to which IncrediBuild writes temporary data.
  • Various fixes and improvements were made to Nintendo Switch compilation acceleration. In order to optimize the performance gain IncrediBuild offers for Nintendo Switch builds, make sure you set a high value to your “Max Compilations” field. This will instruct the Nintendo Switch build system to execute many concurrent compilation tasks which IncrediBuild will then distribute to remote Helpers. In order to set this value in Visual Studio, open the ject’s property page-> “C/C++→General” and set the “Max Compilations” field to a large value (we recommend starting with a value higher than 100).
  • The latest development kit versions of XBox, Sony PlayStation, Nintendo, Unreal Engine and Lumberyard were certified with this new version of IncrediBuild.
  • Fixed a scenario which could have led VsTest unit tests to fail when executed on Helper machines.
  • Fixed an issue in CMake that could have caused the build to fail with “Unknown argument -j”.
  • Fixed a scenario in which tasks couldn’t be distributed to Windows 10 Helpers.
  • Various minor bugs were fixed in IncrediBuild’s user interface, virtualization and the execution engine.

(Back to top)

Changes in Version 8.01

Changes in Version 8.01 (Release Date: March 13, 2017)

Version Highlights

  • IncrediBuild’s Predictive Execution is now certified for Visual Studio 2017 RTM.
  • The IncrediBuild Predictive Execution feature can add additional improvement to Visual Studio 2017 build performance on top of the regular IncrediBuild performance boost.

(Back to top)

Changes in Version 8.0

Changes in Version 8.0 (Release Date: March 7, 2017)

Version Highlights

  • Thanks to our ongoing partnership with Microsoft, IncrediBuild is offered as part of the Visual Studio 2017 experience. As has been the case with previous VS versions, Visual Studio 2017 includes day 1 OOB IncrediBuild support.
  • Certified various scenarios related to distributing tasks between Initiators and Helper with different version of Windows.
  • The Build Monitor window recycling behavior was restored.
  • IncrediBuild now distributes Autodesk’s Maya batch 2016.

Miscellaneous

  • Fixed various issues related to the integration of IncrediBuild with Coverity code analysis.
  • Fixed a scenario in which the BitDefender anti-virus could have failed IncrediBuild with utilizing Helper machines.
  • Added the ability to tune the hard-wired 60 seconds connection timeout that is responsible for the “Timed out waiting for reply from local connection” message.
  • Fixed an issue in which the text {xgTaskID} appears in execution output.
  • Fixed an issue that could cause Sony PS4 (orbis-clang) projects to compile sequentially.

Visual Studio Integration

  • Fixed a bug that prevented Visual Studio Android builds to distribute compilation tasks by default.
  • Fixed a scenario that could have caused Visual Studio builds to fail with the: “MSBUILD : error MSB4166: Child node exited prematurely” message.
  • Fixed an issue in Visual Studio 2012 that could fail IncrediBuild with: “Microsoft.Build.Shared.InternalErrorException: MSB0001: Internal MSBuild Error: Failure during engine shutdown.”
  • Fixed a scenario that could have caused IncrediBuild to fail with “error MSB6006: “midl.exe” exited with code 2212.”
  • Fixed an issue that could have caused IncrediBuild to fail with “Failed to write speculative output…” when executing Visual Studio builds under non-English Windows versions along with the IncrediBuild predictive execution feature and the UseMSBuild flag.
  • Fixed an issue that could have caused an “IBMSBHLP.DLL could not be loaded” error when the IncrediBuild predictive execution feature was being used.
  • A new parameter /vsinstalldir was added to BuildConsole that allows users to provide the path to DevEnv.exe which IncrediBuild will use to execute the build. This feature was added to support the VS2017 multiple workloads option.

Virtualization

  • Distribution of various tasks (including orbis-clang and QT moc) from Windows 10 or Windows 8.1 Initiators to downlevel Helpers is now supported.
  • Fixed various issues that prevented Windows 7 initiators from distributing tasks to Windows 8.1 and Windows 10 Helpers. User Interface
  • Fixed an issue that could have led IncrediBuild to display a wrong time format in the IncrediBuild build monitor.
  • Users can now define ports which are higher than 32767 in the IncrediBuild Agent Settings.
  • Fixed a bug that could cause an access violation when pressing the browse button from the Agent Settings –> Network –> Coordinator.

(Back to top)

Changes in Version 7.31

Changes in Version 7.31 (Release Date: January 1, 2017)

Version Highlights

  • Latest Windows updates are certified along with fixing a non-common scenario that could have caused IncrediBuild to crash.
  • Fixed various issues related to the Ninja build tool.
  • Reverted to the old behavior where a single Build Monitor shows subsequently running builds.
  • Fixed some build issues in scenarios where the English language pack is not installed in Visual Studio. It is highly recommended to install the Visual Studio English language pack when working with IncrediBuild.
  • Fixed a specific issue where the BuildConsole /UseEnv switch combined with the IncrediBuild UseMSBuild option didn’t work correctly.
  • Fixed a rare scenario of missing project index prefix in build output when building Visual Studio solutions.

(Back to top)

Changes in Version 7.3

Changes in Version 7.3 (Release Date: November 17, 2016)

Version Highlights

  • We’re thrilled to announce our continued efforts and partnership with Microsoft has resulted in another day 1 IncrediBuild support, this time for Visual Studio 2017 RC.
  • Predicted Execution is now supported when the UseMsbuild flag is enabled. This means that users running with the UseMSBuild Registry flag enabled or turn on the /UseMSBuild flag in the BuildConsole commandline can potentially enjoy better build parallelization and increased performance.
  • A new feature was introduced for users working with files residing on the network with UNC paths. This feature allows users to force Helper machines to fetch files directly from the network share instead of going through the Initiating machine. Using this feature when network shares are used will increase file synchronization performance and reduce network traffic. The feature relies on the helper machines having access rights to the UNC paths. In order to enable this feature, the flag /no_unc_sync should be added to the IncrediBuild BuildConsole commandline.
  • Various issues fixed for Non-English versions of Visual Studio. When using a Non-English version of Visual Studio 2010 and higher, IncrediBuild will display the build output in English. This change fixes the following issues for Non-English versions of Visual Studio:
    • Double clicking a bar in the build monitor now correctly jumps to the task’s output in builds performed by Non-English Visual Studio versions.
    • Non-English Text that appeared as strange characters in the build monitor is now displayed in English.
    • The color of the bar in the Projects View is now correctly updated to reflect the exit status of each project (Success, Warning or Failure).
    • Fixed an issue in which incremental builds in Non-English versions of Visual Studio could rebuild up-to-date projects in specific scenarios.

New Features

  • Standardized the IncrediBuild BuildConsole command. Added escaped double quotes support \” and other minor fixes.
  • IncrediBuild will no longer require all Visual Studio instances to be shut-down during a version upgrade if the IncrediBuild Visual Studio addon does not require an update.
  • Added the capability of virtualizing DirectX libraries to Helper machines (meaning that Initiating machines’ DirectX libraries will be synched to Helper machines). This behavior can be achieved by adding the /virtualizedirectx switch to the buildconsole commandline.
  • A task’s commandline can now be copied to the clipboard by right-clicking on the appropriate bar representing the task in the Build Monitor.
  • The Build Monitor will now display Visual Studio custom step titles as the bar’s caption.

Miscellaneous

  • Added the option to instruct an Initiating machine to use only 64-bit OS helper machines by adding /only64bithelpers to the buildconsole commandline.
  • Fixed an issue where IncrediBuild agents could appear to periodically change states between offline and online in the Coordinator Monitor.

Visual Studio Integration

  • Certified Predicted Execution to work with .Net Framework 4.6.2.
  • Fixed a rare scenario in which warning and error icons in the build monitor representing a Visual Studio build could be shown in the wrong line.
  • Fixed a specific issue in which IncrediBuild would fail to load a project when batch build dialog was used, with the following error: “Fatal Error: Project ‘X’ cannot be found in the solution file”.
  • Fixed a rare scenario that could cause files that use precompiled headers to be rebuilt during incremental builds in Visual Studio versions 2008 and earlier.
  • Fixed an issue that could cause IncrediBuild to crash while attempting to build certain Xbox One XDK samples.

User Interface

  • Fixed an issue where “Files Built” in build monitor would wrongly count automatically recovered tasks in addition to the executed tasks.
  • Changed the IncreiBuild dark skin theme to better resemble the Visual Studio dark skin one.
  • Fixed an issue that could cause error messages to appear when selecting an option in the Visual Studio plugin list in agent settings.

Virtualization

  • Fixed an issue where 64-bit processes would sometimes be assigned to 32-bit OS helper machines causing executions to fail. 64-bit processes that are attempted to launch on 32-bit OS Helpers will now be automatically recovered, and re-launched on 64-bit machines.
  • Fixed an Issue which caused Visual Studio 64-bit toolsets to be auto-recovered when a Windows 8 or later initiator with Visual Studio 2015 Update 3 would try to employ Windows 7 Helper machines in the build.

(Back to top)

Changes in Version 7.22

Changes in Version 7.22 (Release Date: August 11, 2016)

Visual Studio Build System

  • Fixed an issue where IncrediBuild Visual Studio builds get stuck on the “Preparing build tasks” step, after a major Windows update on Windows 10 Initiators.

(Back to top)

Changes in Version 7.21

Changes in Version 7.21 (Release Date: July 7th, 2016)

Version Highlights

  • Certified support for Visual Studio 2015 update 3.
  • Acceleration of the popular Ninja build system is now certified.
  • IncrediBuild now supports accelerating compilations of the Chromium browser. A sample chromium.ib_profile.xml file was added to the IncrediBuild installation which should be used when configuring Chromium builds to be accelerated by IncrediBuild.
  • IncrediBuild’s BuildSystem.exe now returns exit codes in accordance with how the build finished. Previously, error codes were returned only by the top level buildconsole.exe and ibconsole.exe.
  • Maximum file cache size on Helper machines can now be increased to use up to 30 Terabytes.
  • Certified Microsoft Xbox One XDK up to the March 2016 QFE 4 version.
  • Certified Sony PlayStation SDK up to 3.508.101 version.

Visual Studio Build System

  • Added support for scenarios in which a Visual Studio solution contains more than one project with the same name.
  • Solved a state where long gaps could appear in Visual Studio compilations right after a long link with a “VERBOSE” switch was used.
  • Fixed an issue that could cause errors with Visual Studio 2015 Update 2 builds, when the Initiator and helper machine have different code pages. The error that was addressed is: “error C2855: command-line option ‘/source-charset’ inconsistent with pre-compiled header.”
  • Fixed an issue that could have caused failures when compiling solutions that are using the ilc compiler.
  • Fixed an issue that could have caused IncrediBuild to fail when the build tried to open the Windows Error Reporting.
  • Fixed a scenario that could have led to: “Failed to submit task to queue: Parsing of VC Compiler commandline failed: Could not determine name of OBJ file.”
  • Added a proper handling and message to a scenario in which a specific project is requested to be compiled through the command line but is not contained in the solutions file.
  • Fixed a rare scenario where a project could not be built using IncrediBuild’s batch build with the error: “Failed to load build set. Fatal Error: Project “XXX” cannot be found in the solution file.”

Miscellaneous

  • Fixed an issue in Wii U builds, where .o files could not be found and the following error would appear: “ax: fatal: Unable to open archive file ‘XXX.o’: No such file or directory.”
  • Fixed an issue where IncrediBuild would sometimes fail to install on machines that have non-English localizations with non-English characters in the “user name” or “user group name.”
  • Fixed an issue related to cache clean-up scheduling when machine time is configured to work with 12 hours (AM\PM) time format.

Stability

  • Fixed an issue where inclusion of certain Boost 1.6 headers in Visual Studio 2008 and older solutions, would cause incremental builds to unnecessarily rebuild the entire solution.
  • Fixed an issue where Agent scheduling would work incorrectly when used on machines that are set to the 12H time format.

User Interface

  • The IncrediBuild dark theme now paints the Build Monitor background in a dark color.
  • Fixed an issue that could have led to Agent Settings crashes in specific scenarios.
  • Build monitor now correctly remembers its last window position when it is closed and reopened.

Virtualization

  • Fixed an issue that could cause custom user executable to fail when executed on remote Windows 10 helper machines.
  • Fixed a virtualization issue that could cause custom user executables to fail on Windows 7 helpers when initiated from a windows 8 machine.

(Back to top)

Changes in Version 7.2

Changes in Version 7.2 (Release Date: March 30, 2016)

Version Highlights

  • This version includes previous fixes made in IncrediBuild version 7.11 and version 7.12 that addresses Windows Update KB3135173, KB3126587 and higher that can lead to IncrediBuild failing to execute tasks on remote IncrediBuild Helper Agents. The version fixes the issue for all Windows OS versions.
  • Users can now define the maximum number of cores that will be utilized on their machines when initiating builds. This configuration does not affect the configuration used for helping other builds. This means that you can instruct IncrediBuild to use all your machine’s cores when you initiate builds but only contribute a single core to the pool.
  • Added a new “cache cleanup” mechanism. Cache cleanup scheduling can be configured on the Coordinator Monitor->Settings->Advanced screen.
  • IncrediBuild’s autorecover.ini file, which instructs IncrerdiBuild on which failures to apply the auto recover procedure, is now applied to all the tasks being executed by IncrediBuild and not only Visual Studio compilation tasks (this list can be extended by users).
  • Certified Microsoft Xbox One XDK up to the February 2016 QFE 1 version
  • Certified Sony PlayStation SDK up to 3.008.211 version
  • Certified support for building Unreal Engine using the Windows cross compile toolchain.

Visual Studio Build System

  • Added support for Visual Studio 2015 update 2 CTP (including IncrediBuild’s predictive execution support).
  • Added support for the latest .Net ILC compiler
  • Fixed an issue when using ‘#import’ that could cause compiler error C1083 in VS2015.
  • Fixed an issue that could cause compilation tasks with /analyze flag to fail with C1108 or C1253.
  • Fixed an issue in VS2015 that could lead to distributed compilations failing on Windows 8 and higher in specific conditions.
  • Extended support for older platform toolsets.
  • Extended IncrediBuild predictive execution to support MSBuild version 14.0.24723.2 and MSBuild version 14.0.25008.0.
  • Added support for user’s custom tools, which are executed by the Microsoft Tracker.
  • IncrediBuild allows Visual Studio developers to distribute Fortran compilation tasks by adding an “AllowDistributeFortran” string to the registry with the value “1” under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Xoreax\IncrediBuild\Builder.

New Features

  • When using IncrediBuild to accelerate NMake compilations, double clicking on a failed red bar in Build Monito jumps to a custom pane that displays the task’s StdErr output.
  • Added a new feature to the IncrediBuild profile that allows IncrediBuild for DevTools users to specify per profile tool not to synch back distributed processes output files if such output mask already exists in the Initiator machine. Please refer to the IncrediBuild online manual for further information.

Stability

  • Fixed a scenario that could cause an IncrediBuild warning: “Build object failed to shut down” when various Anti-Virus programs were installed on the Initiating machine.
  • Fixed an issue in distributing 64-bit processes that could have led to access violation on Helper machines.

User Interface

  • Fixed an issue that prevented using “goto next error” using keyboard shortcuts.
  • Batch build window now remembers the last size and position it had before the user closed it.

(Back to top)

Changes in Version 7.1

Changes in Version 7.1 (Release Date: November 30, 2015)

Version Highlights

  • IncrediBuild is now integrated in Visual Studio 2015. Users can directly download and install IncrediBuild within Visual Studio by navigating to New → Project → Build Acceleration menu item.
  • IncrediBuild is now certified for Visual Studio 2015 update 1.
  • The IncrediBuild’s predictive, out-of-order acceleration feature now allows viewing a task’s output even before it reaches the Visual Studio StdOut by double clicking the task’s bar.
  • A new feature allows users to define how many cores they will contribute when acting as Helpers separately from the cores they will contribute when acting as Initiator. In order to use this feature, navigate to AgentSettings → Agent → CPU Utilization.
  • IncrediBuild’s predictive, out-of-order acceleration feature now supports Intel compiler 15.0 under Visual Studio 2015.
  • Certified support for the latest Nvidia CodeWorks for Android and NSight Tegra for Visual Studio.
  • Certified support for Xbox version – August 2015 qfe2
  • Certified support for Sony Playstation version 3.008

Version Stability

  • Fixed a problem that prevented IncrediBuild from accelerating the Marmalade development platform.
  • Fixed an issue related to QuickBuild and Verysoft CTC tool that could have led to access violations.

Version Miscellaneous

  • Fixed an issue that prevented IncrediBuild from using remote Helpers to accelerate NMake builds.
  • The size limit of the IncrediBuild cache was removed.
  • Fixed a bug that caused IncrediBuild to update the PATH variable on a fresh install only after machine restart.
  • Fixed an issue that caused IncrediBuild uninstall to leave some data behind.

Version User Interface

  • IncrediBuild added better support for DPIs higher than 100%.
  • Fixed an issue where tooltip shadows would remain on top of the UI when the tooltips are no longer visible.
  • Fixed an issue that caused off-line IncrediBuild Agents to appear as if their available CPU is more than 100%.
  • Fixed a UI issue when repeatedly clicking Ctrl+F inside the Build Monitor’s output tab.
  • Fixed a minor bug that prevented dragging the Build Monitor sidebar.
  • Fixed an issue where right clicking the context menu in the build monitor would remain in focus when a different window was opened.
  • Filling your Azure password in Coordinator Settings will now hide the password characters.

Version Visual Studio Build System

  • Fixed an issue that prevented IncrediBuild’s build commands using the /Prj=”SomePrj*” parameter to respect the “*” character.
  • Added a new argument “/deploy” to the buildconsole commandline which is equivalent to the same DevEnv command line argument – https://msdn.microsoft.com/en-us/library/tew336h7.aspx
  • Fixed a bug that could have led to zombie compilation tasks that prevented the build from ending.
  • Right clicking and building a project in Visual Studio no longer builds dependencies projects that were not selected to be built in the configuration manager.
  • Fixed an issue that could have led to IncrediBuild unnecessary compiling an additional project when user chooses to debug a specific project using the IncrediBuild for Visual Studio context menu.
  • The “Compile Current File” and “Compiler Open Files” in Visual Studio Addin are no longer supported.
  • Adding support for Unreal Engine work to support Visual Studio 2015.
  • Fixed a bug that caused incremental builds with Intel 15.0 C++ compiler to compile unnecessary files when the out-of-order execution feature was enabled.
  • Fixed a bug that caused failures when building Nintendo 3DS games.
  • Fixed an issue that could have led to Visual Studio shutting down if no IncrediBuild service was running on the machine.
  • Fixed a bug that could have led to: “IncrediBuild: CL Wrapper (GL): Fatal Error: Batch compilation unsupported in this mode”.
  • Fixed a bug that could have led to linking resulting in error: “error MSB6006: “link.exe” exited with code -1073741787.”.
  • Fixed a bug that could have led to an error: “Failed to reallocate virtual stream” when having a solution with large PDB files.
  • Fixed an issue in Visual Studio that could have led to “Parsing of VC Compiler commandline failed: Could not determine name of OBJ file.”.
  • Fixed an issue that could have caused a “Failed to reallocate virtual stream” error.
  • Version Visual Studio Integration
  • Fixed a bug that caused the VS2015 add-in to be seen in Agent Settings even if VS2015 was not installed on the user’s machine.
  • Fixed an issue that caused Nintendo Wii U builds to not execute inter-project tasks in a parallel manner

(Back to top)

Changes in Version 7.0

Changes in Version 7.0  (Release date: August 10, 2015)

Version Highlights

  • Added support for the latest Windows 10 version.
  • Added support for the latest Visual Studio 2015 version.
  • IncrediBuild is now bundled as part of the NVIDIA GameWorks solution.
  • IncrediBuild highly accelerates the latest version of Unreal Engine 4.9.0 for both compilation and baking. Benchmarked results for Unreal Engine compilation show 7x accelerating and 3x acceleration for baking.
  • IncrediBuild certified acceleration of GTest unit testing.
  • IncrediBuild’s memory usage was reduced.
  • IncrediBuild will no longer distribute tasks to Vista Helpers when building VS2012 solutions and higher.

New Features

  • Added a new feature that enables users to highlight all error bars in the Build Monitor. In the Build Monitor menu navigate to: View->Mark Error Bars.
  • Added a new switch /NO_DOTNET_VIRT for IbConsole / XgConsole command line. When this switch is specified in the command line it instructs IncrediBuild not to virtualize the .NET environment of the Initiator machine to the Helper machines. This switch was added to address .NET incompatibilities in a mixed OS environment.
  • When an image that includes IncrediBuild will be placed on a new machine/VM, IncrediBuild will redefine the amount of cores that will be utilized in this machine upon first activation according to the machine’s hardware (unless a specific number of cores was provided by the user in the Registry or Agent Settings).
  • Detailed graphs for waiting / ready tasks were added to the IncrediBuild Build Monitor.
  • Visual Studio Build System
  • Increased build performance of Intel compiler based solutions under Visual Studio 2010 and higher by applying predictive execution to Intel compiler.
  • Some increased performance in VS2010 and above in certain scenarios when using PCH files.
  • Fixed an issue where type library import could fail under Visual Studio 2013.
  • Fixed a minor bug in which the IncrediBuild VS2015 add-in check-box remained unchecked although the plug-in was installed.
  • Fixed some esoteric dependency evaluation issues in VS2005 and VS2008 that could have led to files not being rebuilt if their include file changed.
  • Fixed an issue that prevented IncrediBuild from compiling a single file when trying to do so from the IncrediBuild menu for Visual Studio.
  • Fixed an issue that could have led to a “failed to sign assembly” error in C#.
  • Fixed an issue that could have led to IncrediBuild unnecessary compiling an additional project when user chooses to debug a specific project using the IncrediBuild for Visual Studio context menu.
  • Solved an issue of distributing C# compilations to a Helper with a Vista OS.

Virtualization

  • Fixed some scenarios that could have led to large memory consumption in highly parallel builds that could result with an error of: “Failed to allocate virtual stream”.
  • Fixed a rare scenario that caused IncrediBuild to stop distributing tasks during a build.
  • Fixed a rare scenario that could have caused distributed custom processes to hang when working in a mixed Windows 7 – Windows 8 environment.

(Back to top)

Changes in Version 6.1

Changes in Version 6.1 (Release Date: March 31, 2015)

Version Highlights

  • Predicted execution now supports the nvcc.exe Cuda compiler under Visual Studio. IncrediBuild’s predicted execution will now execute nvcc compilations under the same project in parallel as opposed to Visual Studio’s behavior, which executes multiple nvcc compilations in the project in a sequential manner. This feature highly accelerates build times of Visual Studio projects containing multiple nvcc compilation tasks.
  • A new option “AllowPredictedBatch” was added to IncrediBuild’s profile.xml to allow users to control parallelization of custom build tools and custom build rules in Visual Studio 2010 and above. This option will highly accelerate execution of projects that have many build tool files, since it will allow parallelization of these build tools, while under Msbuild these tools will run on only 1 CPU core in a sequential manner. For more information please see this page.

New Features

  • IncrediBuild now further accelerates Qt under Visual Studio 2010 and above, by executing moc processes in parallel and in a distributed manner – a sample Qt profile.xml was added to the installation folder under the “Profiles” subfolder. This xml profile demonstrates how to configure the Qt solution for optimal build acceleration results using the new “AllowPredictedBatch” feature.
  • A new “AllowRemoteIf” option was added to IncrediBuild’s profile.xml to allow conditional setting of whether a process should run remotely based on the parameters it receives in its command line. This option can be used to control certain I/O heavy instances of a particular tool to run on the local machine only (e.g. an instance of the GCC compiler which is invoked to perform a link and not a compilation) while other instances of the tool would be distributed to remote machines (such as the GCC compilation tasks).
  • Certified IncrediBuild support for XBox FEB 2015 SDK.
  • Certified IncrediBuild support for Play Station SDK version 2.000.
  • The gcc and cl tools will now be executed on the local machine, if they are invoked to link rather than compile. If you want to be able to distribute GCC link jobs to remote machines, you need to create a registry value “RunGCCLinkRemotely” under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Xoreax\IncrediBuild\Builder and set its value to 1.

Stability

  • Fixed an error caused when cl.exe is launched under a Visual Studio build with no arguments.
  • Fixed a dependency evaluation issue when building Boost 1.57 dependent projects with Visual Studio 2008 and older.
  • Fixed dependency evaluation failure for boost preprocessor library.
  • Fixed an issue where process output would be misarranged when running in predicted execution mode.

Visual Studio Build System

  • Predicted execution is now supported up to Visual Studio 2015 CTP6.
  • Fixed an issue of IncrediBuild not creating target directory in Visual Studil 2008.
  • Fixed failure to build Universal Projects in Visual Studio 2013.
  • Distribution support added for the new csc2.exe executable introduced in Visual Studio 2015.
  • Fixed an issue where type library import fails under Visual Studio 2010 and newer versions.
  • Fixed a problem when .tlh files are not created under Release configuration under Visual Studio 2010 (in specific scenarios or always?).
  • Fixed an issue with launching .vcxproj buildconsole command lines with Visual Studio 2013.

Miscellaneous

  • Fixed ADDTOPATH in silent installer. Now correctly adds IncrediBuild installation path to the %PATH% system variable.
  • Fixed incorrect message box when trying to load license.

(Back to top)

Changes in Version 6.0

Changes in Version 6.0 (Release Date: January 7, 2015)

Version Highlights

  • IncrediBuild’s “Predictive Execution” feature which highly optimizes Visual Studio’s build parallelization and performance is now enabled by default on all Agents.
    With the Predicted Execution feature, IncrediBuild is able to execute more compilation processes in parallel in Visual Studio 2010 and higher, further accelerating build times.
    For example, when project “B” depends on Project “A”, IncrediBuild will be able to execute in parallel both projects’ compilations while building. Without IncrediBuild, this will result in consecutive executions.
  • Visual Studio 2015 Preview Edition is now fully supported by IncrediBuild.
  • IncrediBuild now accelerates Visual Studio Android builds.
    IncrediBuild’s Predictive Execution highly accelerates Visual Studio builds, allowing developers to execute parallel compilation tasks in an optimized manner. IncrediBuild will boost Visual Studio Android builds even when building on a standalone workstation.
  • IncrediBuild now supports building Visual Studio Universal Projects.
  • IncrediBuild now supports Visual Studio Community Edition.
  • Official support for PS4 SDK 1.700 was added.

New Features

  • IncrediBuild’s “Predictive Execution” feature which highly optimizes build parallelization and performance now supports Visual Studio 2013 Update 4.
  • Using the “Rem IncrediBuild_AllowOverlap” flag from within custom steps and build events will instruct IncrediBuild to execute these steps in parallel to consecutive tasks thus further improving build performance.
  • Added out-of-the-box support for CMake acceleration under the Make and build tools solution.
  • A new feature allows users to pass additional arguments to MSBuild when using the buildconsole command’s “/usemsbuild” switch.
    To use this feature /msbuildargs=”/myarg1 /myarg2″ should be added to the buildconsole command.

Visual Studio Build System

  • IncrediBuild adds support for multiple .res files within a dll in Visual Studio 2008 and 2005.
  • Fixed a rare issue of empty tlog files that could have resulted in an access violation in IncrediBuild.
  • Fixed an issue that prevented IncrediBuild to correctly execute a compilation command when there were spaces inside the /wd compiler switch that could have resulted in: “Command line error D8021: invalid numeric argument”.
  • Fixed a bug that prevented executing custom steps remotely in Visual Studio 2010 and higher when using the “rem incredibuild_allowremote” flag.
  • Fixed a bug where multiple /nologo switch instances could have led to rc.exe failures.

Stability

  • Fixed an issue that could have led to IncrediBuild exiting with exit code 217.
  • Fixed a bug that resulted with IncrediBuild “assertion failure (x:\dev\cm\StringLists.pas, line 1987)” when cl.exe was executed without any arguments.
  • Fixed an error (CLANGCL: error: error reading ‘xxxxxxx’) that could have appeared in remote machines when building using PS4 SDK 1.700.
  • A new registry string value “DisableStdOutIdentify” should be created and set to 1 under
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Xoreax\IncrediBuild\Builder\
    to fix scenarios in which “XgTaskID…” appears in the build output.
  • Solved an issue that could have sporadically caused the Coordinator to become unreachable.

User Interface

  • Fixed an incorrect message that popped up when attempting to load a license with expired maintenance.
  • Fixed an issue with remote agents still showing license details in the Coordinator Monitor even though license was already unloaded from the Coordinator machine.

Virtualization

  • Added virtualization support for operating system dll “wer.dll”.
    Previous use of this dll could have caused an error similar to “STATUS_ENTRYPOINT_NOT_FOUND”.

Miscellaneous

  • Fixed a bug that prevented developers from using up to 8 cores after IncrediBuild’s trial license has expired.
  • Fixed a bug related to buildconsole /disable feature.
  • Fixed a problem of a warning not given to developers when building on an Agent without a license.
  • Fixed a bug that could cause assemblies signing issues when using a “buildconsole /command=” interface.
  • Fixed a license loading issue that could have resulted in error: “Load License Error: Stream read error”.

(Back to top)

Changes in Version 5.5.2

Changes in Version 5.5.2 (Release Date: August 27, 2014)

  • Minor changes related to trial licence

(Back to top)

Changes in Version 5.5.1

Changes in Version 5.5.1 (Release Date: August 8, 2014)

Visual Studio Integration

  • Playstation 4 SDK certified up to 1.750.
  • Added predictive execution support for VS2013 update 2. To benefit from enhanced acceleration in Visual Studio 2010 and above, activate the predictive execution feature (Agent Settings->Visual Studio Builds->Advanced->Predictive Execution).
  • Fixed an issue in VS2010 and above when using Rem_IncrediBuild directives in custom steps that could have led to error messages similar to “Cannot open file: “C:\…\cstep_{GUID}.bat””

Stability

  • Fixed a bug that could have led to backup Coordinator not being available when primary Coordinator goes down.
  • Double clicking a license will now execute the Coordinator Monitor with administrative rights.
  • Failing to load an IncrediBuild license due to limited permissions (non-administrative user or UAC limitations) will no longer prevent the user from trying to load the license again using the correct authorization level

(Back to top)

Changes in Version 5.5

Changes in version 5.5 (Release Date: July 20, 2014)

Highlights

  • IncrediBuild to accelerate code analysis solutions from KlocWork and Coverity. For further information please contact
    [email protected]This email address is being protected from spambots. You need JavaScript enabled to view it.
    .
  • IncrediBuild Improved performance for Visual Studio 2010\2012\2013. Projects that contains many units can be expected to gain meaningful additional performance.
  • A new beta feature is introduced to further accelerate Visual Studio 2010\2012\2013 compilations by using “predictive execution” mechanism which allows IncrediBuild to highly increase throughput. In order to activate this feature you need to enable the “predictive execution” option in your local machine under Agent Settings->Visual Studio Builds->Advanced. This feature can offer a meaningful additional acceleration, especially for solutions that contain many projects. (This feature is currently not supported and should not be enabled in CUDA and Nintendo solutions).
  • Added support for latest Visual Studio updates: VS2012 update 4, VS2013 update 1, VS2013 update 2.
  • IncrediBuild fully supports Windows 8.1 update.
  • IncrediBuild now highly accelerates Android NDK builds.
  • Xbox One XDK is certified up to XDK July 2014 release.
  • Added support for latest CygWin framework (August 2013 version).
  • IncrediBuild to highly accelerate NVidia’s NSight Tegra for developing Android development using Visual Studio (https://developer.nvidia.com/nvidia-nsight-tegra)

(Back to top)

Changes in Version 5.0

Changes in Version 5.0 (Release Date: December 10, 2013)

Highlights

  • Incredibuild now fully supports Visual Studio 2013.
  • IncrediBuild new activities for Microsoft Team Foundation Server (TFS) acceleration.
  • Full support for Windows 8.1 OS.
  • Certified C# acceleration.
  • Certified MSTest acceleration.
  • New and improved IncrediBuild help file.
  • A new beta feature was introduced, that allows better tasks parallelization for full rebuild, resulting in an increased performance (up to 50%!), depending on the solution’s structure.
  • To activate it, set the following registry value:[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Xoreax\IncrediBuild\Builder]”PredictedExecutionMode”=”1″

New Features

  • IncrediBuild provides new activities for accelerating Microsoft Team Foundation Server (TFS) work flows. Supported platforms are TFS2010, TFS2012 and TFS2013. For further information please contact

    This email address is being protected from spambots. You need JavaScript enabled to view it.
  • New virtualization features added to support Xbox One’s latest SDKs. These features resolve issues such as “c1xx : fatal error C1001: An internal error has occurred in the compiler”.
  • GnuMake was added to the Make & Build tools package.
  • A new registry value under Builder\CtrlBreakWait was introduced to give users full control over IncrediBuild’s CtrlBreak timing when a build is aborted by user.
  • BuildConsole supports a new switch: “/UseMSBuild” to specifically instruct IncrediBuild to use MSBuild’s build engine instead of the default Visual Studio’s DevEnv (this is especially useful for C# and TFS).
  • BuildConsole now supports a new switch: “/OutDir” to specify the build output directory (this feature is only supported in conjunction with the new /UseMSBuild switch ).
  • C# solution acceleration is now supported in trial mode.

Performance

  • The default “max number of agents that will participate in a build” is now increased to 150.
  • The default number of links that will be executed in parallel is now equal to the number of logical cores that the Initiating machine has.

Visual Studio Build System

  • Added support in VS2012 for running a specific vcxProj file with references using BuildConsole’s /command and /NoRecurse switches.
  • Eliminated build gaps in VS2008 and bellow in scenarios where _MSC_EXTENSIONS predefined was used.
  • Using a profile in a BuildConsole command will allow internal optimizations of time-consuming custom steps.
  • Fixed a bug in VS2010 and above that led to systematic warning during link when targeting vc9 runtime.

Visual Studio Integration

  • Fixed a bug in Visual Studio plug-in that could have led to an error of “invalid floating point operation”.
  • Fixed a bug that could have led Visual Studio to crash when using “auto hide” windows.

Stability

  • Fixed a problem in Windows8 distribution that could have led to exit code 0xC0000142.
  • Fixed a scenario that could have led to Xbox One compilation failure when the “Restart on local machine when possible” option was used.
  • Fixed a bug that could have led to “fatal error LNK1181: cannot open input file…” when a long relative paths were specifically used.
  • Fixed a bug that could have led to “error C2857: ‘#include’ statement specified with the /Ycstdafx.h command-line option was not found in the source file” when stdafx.h is manually set to a specific location.
  • Fixed a rare scenario in which BuildConsole incorrectly exits with “0” when the /stoponerrors switch was used.
  • Fixed a bug that could have led to “Directory cache error: Cannot handle directory request for an empty string” when an empty .PDB file name was used.
  • Fixed a bug in Nintendo 3DS platform that led to “armcc : error C3065: type of input file ‘/FIfilename’ unknown”.
  • Fixed some issues that could have been caused when Bash processes exited with an error code when used in conjunction with the “Restart on local machine when possible” feature turned on.
  • Fixed some rare issues in VS2008 and below when a non-standard Intel compiler projects where used.
  • Fixed a bug that made the Coordinator Monitor unresponsive and required a lot of CPU when many Login / Logoff actions where performed on the Coordinator machine.
  • Fixed a bug with Cygwyn that could have led to a failure: “Couldn’t fork: Resource temporarily unavailable”.
  • Fixed a rare case in which executing a distributed process using CreateProcessA resulted in Access Violation.
  • Fixed a bug in VS2008 that led to a “fatal error C1859”.
  • Fixed a bug that could have led to “Unexpected error : Virtual address space usage exceeds 512MB limit”.
  • Fixed a bug that could have led to an “Unregistered packet class” error on local machines.

(Back to top)

Changes in Version 4.62

Changes in Version 4.62 (Release Date: July 22, 2013)

Highlights

  • Added support for Xbox One July 2013 SDK.

(Back to top)

Changes in Version 4.61

Changes in Version 4.61 (Release Date: June 24, 2013)

Highlights

  • In this version, beside various stability fixes, we have included all PlayStation product family into IncrediBuild’s Visual Studio integration, allowing PlayStation game developers to enjoy from all our VS feature rich offering.*
  • All game developers can now build once for all IncrediBuild supported game platforms: PS4, PS-Vita , PS3, PS2, Xbox One, Xbox 360, Nintendo Wii U, Nintendo Wii, Nintendo 3DS and any PC games. There is no need to divide each game platform to a different solution.
  • The version is performance optimized for the various tools executed by PlayStation’s build system, including optimized I/O access, performance, bar captions and more.
  • *Please note that PlayStation users might need to set the “Maximum Concurrent C++ compilations”  Visual Studio switch with a large value (200 or more) in order to make sure IncrediBuild has as many as possible compilation tasks executed in parallel:
  • In Microsoft Visual Studio, go to Tools>Options>Projects and Solutions>VC++ Project Settings>Maximum Concurrent C++ compilations and set the value to 200 or more.

Stability

  • Fixed a bug in which Windows Vista Helpers could have caused build to fail.
  • Fixed a bug that could have led IncrediBuild to drop off using only the local (Initiator) machine’s cores.
  • Fixed a bug that could have led to 64-bit Intel compiler failures.
  • Fixed a bug in which Windows 2008 server Helpers could have caused build to fail.
  • Fixed an issue that could have led to the error: “Fatal error C1902: Program database manager mismatch” on Helper machines.

Visual Studio 2010 & 2012

  • Fixed a bug that could have caused an MSB3721 error.
  • Fixed an issue that could have caused an Access Violation exception when executing a build.
  • Fixed an issue of COM inter-op registration as part of a batch file execution in Visual Studio
  • Fixed a scenario in which IncrediBuild could have returned a 0 exit code although build failed in non-English Visual Studio
  • Fixed a scenario in which IncrediBuild could have returned a 0 exit code although build failed when directive /StopOnErrors was used in IncrediBuild’s BuildConsole command
  • Fixed a bug that could have led to Intel compiler execution failure under specific circumstances leading to the following message: “Failed to create process: ;…”
  • Fixed an issue that could have led to RC1107 error

Visual Studio prior to 2010

  • Fixed an issue in Visual Studio where  post build step were executed even when no changes were made
  • Fixed an issue in “Windows Mobile 6 Professional SDK” that could have led to error LNK2005
  • Handled a previously unsupported Intel compiler directive /Qdiag-disable
  • Fixed a scenario that could have led to “cl : Command line error D8003 : missing source filename” error
  • Added the ability for pre-compiled headers to reside in a different folder level of the project file.

(Back to top)

Changes in Version 4.6

Changes in version 4.6 (Release Date: April 30, 2013)

Highlights

  • Windows 8 OS is now fully supported by IncrediBuild, whether installed on an Initiator or a Helper machine.
  • IncrediBuild now enables distribution and interception of 64-bit processes, providing the ability to execute 64-bit processes on remote machines.
  • Sony PS4 builds can now be accelerated using IncrediBuild by building using Sony’s VSI menu item “Distributed Solution Build”
  • IncrediBuild now supports Visual Studio 2012, updates 1 and 2.
  • New samples were added to IncrediBuild showing its ability to accelerate among others: compression, image processing, conversion.
  • IncrediBuild can now accelerate VxWorks compilations when VxWorks floating license model is used.
  • Beta support for C# projects distribution is currently available by contacting IncrediBuild’s support. C# projects distribution provides acceleration of solutions containing many C# projects.

New Features

  • A C# project bar will now display the project’s output file name.
  • Make & Build tools package now accelerates DevEnv command line.
  • IncrediBuild now supports the latest Nintendo 3DS CTR environment.
  • The vcxProj file type was added to the project type’s list, which can be opened via the tray icon.
  • Initiator machines using the .Net 4.5 framework will no longer use XP machines as helpers (this is due to the  limitation running the .Net 4.5 framework tracker on XP).

Performance

  • Eliminated sporadic gaps that could have been caused by MSBuild Tlog handling.

Stability

  • Fixed a rare bug in VS2008, which caused IncrediBuild to incorrectly substitute defines with quotes.
  • Fixed a bug in VS2008 resulting in: “Task queue management failed – Precompiled header define map unavailable Error”.
  • Fixed some bugs when executing MSBuild commands using “BuildConsole /command”.
  • Fixed rare scenarios in which the build monitor showed a failed build, although it completed successfully.
  • Fixed a bug resulting in error message: “PDB Management error : Failed to create process”.

Virtualization

  • Improved interoperability of XP OS machines executing .Net processes on Helper machines with other operating systems.

Visual Studio Build System

  • Fixed an issue that caused projects using the latest Marmalade SDK in VS2008 to fail.
  • When initiating a request for a specific project to be built, IncrediBuild will now skip checking the integrity of the solution file.
  • When compiling a single project with the BuildConsole command line, IncrediBuild will choose the relevant Visual Studio version according to the solution file.
  • Fixed a bug in VS2010 resulting in: “VS2010: ‘/cstep’ is not recognized as an internal or external command”.
  • Fixed a bug that could have caused failures in custom steps execution in 64-bit XP sp2 OS.
  • Fixed a bug that could have led to un-labeled bars in the build monitor.
  • Fixed a bug that could have led to wrong environment loading when building C# 64-bit projects.

(Back to top)

Changes in Version 4.51

Changes in version 4.51 (Release Date: December 2, 2012)

New Features

  • Added official support for Boost 1.49 and 1.50.
  • IncrediBuild for Make & Build Tools now accelerates Visual Studio Express 2010 and Visual Studio Express 2012.
  • IncrediBuild for Make & Build Tools now accelerates SCONS and WAF build tools.
  • Added support for PCH projects for VSI Café (Nintendo Wii U).
  • IDL steps are now distributable to remote machines in VS2010 and VS2012 by setting a registry flag.
  • Added the ability to open \??\Nsi device from NtCreateFile by tasks executed on remote machines.
  • IncrediBuild now supports VS2010 solutions that are opened in VS2012 and not being upgraded to VS2012.

Performance

  • Increased pre-link Visual Studio calculation speed by an additional ~20%.

User Interface

  • Windows 8 is now correctly represented in the Coordinator Monitor.
  • Fixed an issue that resulted in a non changing Tray Icon color according to build result status.
  • Fixed an issue of a rare scenarios in VS2010 where the Build Monitor -> project display, is not displaying the correct status color.
  • Visual Studio will no longer throw an exception dialog when user cancels debugging execution.

Stability

  • Fixed a bug that caused compilation tasks and build processes to hang.
  • Fixed an issue (Xbox and regular builds) resulting in – “CL : System error : -2146697203” message.
  • Fixed an issue in VS2008 and VS2005 leading to – “Fatal error: – Precompiled header define map unavailable – Precompiled header define map unavailable”.
  • Fixed a bug resulting in – “PDB Management Error: Failed to create process: ; mspdbsrvx -start -spawn”.
  • Fixed a bug resulting in – “CL Wrapper (GL): Reference object file size differs from final object file size”.
  • Fixed a bug resulting in – “IncrediBuild: CL Wrapper (GL): Fatal Error: Batch compilation unsupported in this mode”
  • Fixed a bug resulting in – “error MSB6006: CL.exe exited with code 4”.
  • Fixed a bug resulting in – “C2859: vc90.pdb is not the pdb file that was used when this precompiled header was created, recreate the precompiled header”.
  • Fixed a bug resulting in – “Cannot apply file changes while file is being closed”.
  • Fixed a bug where IncrediBuild might sometimes crash while pushing updates to XP and Windows server 2003 machines.
  • Fixed a scenario where #import resulted in – “fatal error C1083: Cannot open include file” upon first build.
  • Fixed a scenario that led to Link fatal error LNK1170.
  • Fixed scenarios in which a space character was added after a parameter that was passed to an external tool in VS2010.
  • Fixed scenarios in vs2008 and vs2005 containing C# projects that sometimes caused C++ projects to be rebuilt unnecessarily. In order to activate this fix please contact
    [email protected]This email address is being protected from spambots. You need JavaScript enabled to view it.
    .

Miscellaneous

  • Fixed a bug that requested Make & Build tools license when using XgConsole without profile xml file.

(Back to top)

Changes in Version 4.5

Changes in Version 4.5 (Release Date: September 6, 2012)

Highlights

  • IncrediBuild for Visual Studio 2012.
  • Version 4.5 offers significantly enhanced build performance and scalability for VS2005-VS2012 and other build tools as compared to previous IncrediBuild versions. This version focuses on link time reduction, memory consumption and network and IO optimizations.
  • IncrediBuild supports the pre-release version of Microsoft Windows 8 on initiating machines.
  • IncrediBuild now supports an unlimited number of cores on build servers.
  • New independent solution available for Make & Build Tools acceleration.
  • Acceleration for New Third-Party Applications
  • WiiU Cafe compiler for all Visual Studio versions and other build tools.
  • KlocWork code analysis.
  • CUDA compilations in all Visual Studio versions and other build tools.

Miscellaneous

  • Introduced a new licensing mechanism for multi-cores including automatic license assignment algorithm according to workstation cores.
  • Trial license now supports up to 4 agents with up to 8 cores each.
  • Renamed the XgConsole tool to IBConsole. XgConsole tool will remain for backward compatability.
  • New Features
  • New independent solution available for Development Tool acceleration enables the acceleration of the entire development cycle.
  • Added the ability to specify max parallel links to be performed in VS2010 and VS2012.
  • Added the ability to handle non-Latin characters in processes and system environment.
  • Added the ability to execute batch builds sequentially.
  • Custom steps’ output is now taken under consideration when performing pre-processing in VS2008 and VS2005.
  • informative auto-recovery message was added to scenarios in which a remote helper cannot be assigned.
  • Added support for COD files generation.

Performance

  • Performance improvement and scalability of Microsoft, Intel and XBox compilers build and link time.
  • Reduced the maximum amount of virtual memory consumed by link tasks in most common scenarios.
  • Improved performance in IO synchronizations between Initiator and agents resulting in accelerated performance, especially when utilizing many helpers.
  • Reduced virtual memory size of IncrediBuild when there is a lot of output writing.
  • Max default number of cores to participate in a build was increased to 60 in order to improve performance.
  • Improved idle CPU level detection leads to more optimal task assignments.
  • Optimized network traffic infrastructure resulting in improved network performance.
  • Optimized memory allocations during pre-processing for VS2008 and VS2005 resulting in optimized memory consumption.
  • Optimized repetetive/continous connection attempts to helpers in cases where connection attempt has failed.
  • Added a better more selective use of data compression for data sent from Helper machines to Initiator.
  • Increased the number of projects that can be built in parallel on workstations where the VS2010’s options dialog was never opened.
  • Minimized the number of directory scans performed in the initiating machine.
  • Optimized pre-processing cache file size.
  • Reduced IO operations of Build Monitor.

User Interface

  • Added support for double clicking a bar or progress bar when using a single core, working with non-Latin languages or compiling specific files from Visual Studio IDE.
  • Fixed a bug that caused project name and configuration not to appear as expected when hovering over a bar in VS2010.
  • Double clicking an error bar in VS2010 and VS2012 now always redirects to the relevant output window.
  • Visual Studio Build System
  • Faster initialization of IncrediBuild’s build service.
  • IncrediBuild now co-exist with VTune projects.
  • IncrediBuild now supports a scenario in which a project references itself that previously resulted in “Error: Failed to initialize Build System” message.
  • IncrediBuild now cleans files that previously remained in the temp folder.
  • Fixed a bug in which errors in the project utput tab are not clickable.
  • Fixed a bug – the following warning appears :Warning appears – Warning: Debug info processing incomplete.
  • Fixed a bug – building multuple configurations result in failures.
  • Fixed a bug – a solution that includes Nintendo Cafe platform is forced to be built in standalone mode (even when no Cafe project is built).
  • Fixed a bug in which PDB file name in VS2008 and VS2005 was different when using $(ImageName) in property sheet.
  • Fixed a bug in VS2008 and VS2005 in which a manifest file was being embedded twice in specific scenarios.
  • Fixed a bug in which no manifest was embedded when running incremental build in release configuration in specific scenarios.
  • Fixed a bug in which C# projects were built even though no changes were made.

Stability

  • Preventing Dr. Watson anti-virus from causing compilation tasks to hang.
  • Optimized IncrediBuild virtual memory usage, solving rare issue: “Virtual address space usage exceeds xxxMB limit”.
  • Fixed a bug which resulted in a “Failed to parse text” message in specific scenarios in Asian languages.
  • Fixed a bug of LNK1123 in VS2005 and VS2008 when including duplicate .res files through the property sheet.
  • Fixed a bug in which .res file was not found in rare scenarios in VS2008 ans VS2005.
  • Fixed a bug in which a wrong path was used by IncrediBuild’s auto-installer.
  • Robocopy and IncrediBuild now co-exist in VS2010.
  • Fixed a bug that casued distributed executables without proper file properties to fail with ‘Target queue management failed’ message.
  • Fixed a bug in which intermediate logging level caused an initialization failure.
  • Fixed a bug that caused BuildSystem to raise an exception upon initialiization in rare scenarios.

(Back to top)

Changes in Version 4.0

Changes in Version 4.0 (Release Date: February 8, 2012)

  • Introduced early adaptations for Visual Studio 2011 Developer’s Preview edition.
  • Added support for distribution of custom steps & build tools for VS2010.
  • Added new management capabilities to enable full control over the behavior of custom build steps and build tools.
  • Added official support for CUDA & OpenCL build acceleration.

Support for New Third-Party Applications

  • Sony PS3 builds for VS2010.
  • MicroFocus DevPartners for VS2010.

Visual Studio 2010 Build System

  • Introduced a new local project compilation option by adding an IB_RunLocal definition to the preprocessor definition for a particular project.
  • Added the ability to distribute custom steps & build tools for VS2010.
  • Added full control over behavior of custom build steps and build tools through a profile XML by using the XGE Interception Interface.
  • Added support for complex VS2010 dependencies scenarios.
  • Added the ability to define specific tool exit codes as successful.
  • Added support for cl_add and cl_rem.
  • Added “run as admin” for batch build execution in order to prevent UAC issues by adding a registry value “RunAsAdmin” with the value 1.
  • Excluded local CPUs from the number of utilized CPUs in the agent settings dialog (now refers only to remote helper CPUs).
  • Added the ability to jump to the relevant output by double-clicking a locally executed task.
  • Updated logging verbosity to copy from Visual Studio settings.
  • Added support for project name which resides under a folder with the same name.
  • Fixed mt.exe error c101008d.
  • Fixed a bug in which a process couldn’t access a .tlog file.
  • Fixed a bug that occurred when spaces were used inside preprocessor definitions.
  • Fixed a bug in BuildConsole /SetEnv directive for VS2010 projects.
  • Fixed several minor bugs in BuildConsole.
  • Fixed a bug caused by MSBuild limitation which forces the existence of a Win32|Debug configuration.
  • Fixed a rare scenario in which BuildSystem would freeze.

Visual Studio 2003/2005/2008 Build System

  • Enhanced performance in the preprocessing phase.
  • Optimized acceleration for the Boost library.
  • Added support for $(NOINHERIT) macro in the Linker additional dependencies property.
  • Added support for empty /Yc field (PCH file usage configuration).
  • Fixed a bug in which IncrediBuild re-linked a project when an additional manifest file was added.
  • Fixed a rare scenario in which a file location was manually changed to the TargetDir in the vcproj file.
  • Added support for rare MIDL output files.

Miscellaneous

  • Added virtualization for SSPICLI.dll.
  • Reduced Coordinator service IO.
  • Fixed various Nintendo 3DS integration issues.
  • Fixed BuildConsole build percentage progress.

Xoreax Grid Engine (XGE) Interfaces

  • Added ability to collect the output of xgsubmit tool to a file by adding xgWait /report=.
  • Added support for various special characters inside XgConsole command.

(Back to top)

Changes in Version 3.61.1

Changes in Version 3.61.1 (Release Date: September 1, 2011)

Visual Studio 2010 Build System

  • Added support for using IncrediBuild with Intel compiler 10.1.
  • Added support for buildsystem initialization without registry key ‘MSBuildLoggerVerbosity’.
  • Added support for building a VS2010 vcxproj in buildconsole with multiple configurations.
  • Added support for building a solution with a vcxproj name different than the project name as seen in the VS IDE.
  • Added support for running 64bit builds on a 32 bit machine, using the correct environment settings.
  • Configuration information in the project tab is now showing the project configuration instead of the solution configuration.
  • Fixed a bug in which link error LNK1112 is seen when building in x64 configuration.
  • Fixed a bug in which errors in the project output tab are not clickable.
  • Fixed a bug in which cannot open lib.exe error was seen.

Stability

  • Fixed a bug in which the build hangs when running a vcxproj buildconsole command.
  • Fixed a bug in which Microsoft C/C++ optimizing Compiler crashes during the build process.
  • Fixed a bug in which VC Compiler crashes when using /Zm and compiling simultaneously locally.

(Back to top)

Changes in Version 3.61

Changes in Version 3.61 (Release Date: August 22, 2011)

Visual Studio 2010 Build System

  • Visual Studio 2010 build system is now compatible with Visual Studio IDE build system to avoid known MSBuild compatibility problems.
  • x64-specific tools and environment are now used in x64 platform builds.
  • Single-file compilation is now supported.
  • BuildConsole now supports multi-configuration builds.
  • resgen.exe on 32-bit OS with toolkit 9.0 is now supported.
  • IncrediBuild now co-exists with Bullseye installations.
  • /setenv BuildConsole flag is now supported.
  • double quotes in the PATH environment variable are now supported.
  • Project filenames which are different from their corresponding IDE names are now supported.
  • Added support for vcproj files saved in UTF-8 encoding.
  • Spaces inside preprocessor definitions are now supported.
  • Fixed a bug that caused certain native x64 tools (midl, link, rc and others) to crash during the build process
  • Fixed a bug in which custom build and link steps always run.
  • Fixed a bug in which pre-link events always run.
  • Fixed a bug in which IncrediBuild continues to link after the pre link step failed.
  • Fixed a bug in which referenced projects that were not part of the solution were still built.
  • Fixed a bug in which the wrong configuration was built when running BuildConsole with the /prj switch.

Visual Studio 2003/2005/2008 Build System

  • Considerably improved incremental build times.
  • comments in Japanese preprocessor statements are now supported.
  • INCLUDE variable definitions which contain double quotes are now supported.
  • $(INHERIT) macro is now interpreted correctly in all scenarios.
  • Manually changed TargetDir variable definition in vcproj files is now supported.
  • Added support for Assembly Reference Search Paths.
  • #using statements referencing an assembly already referenced by the project are now supported.
  • Custom build steps including the string ‘error’ are no longer automatically considered as failed.
  • Added support for TRUE/FALSE values for the /EHsc compiler switch(cmake bug).
  • /NOLINK BuildConsole option now prevents post-build steps from running.
  • Double quotes in the intermediate directory specification are now supported.
  • Warning “Importing type library directly is recommended” no longer appears when using .net assemblies.
  • Error “fatal error: could not find assembly” no longer appears unnecessarily.
  • Smart devices cab projects are now supported.
  • Changes to resource files are now correctly detected in Nintendo 3DS builds.
  • ForceInclude is now supported in Nintendo 3DS builds.
  • /prj=”*” BuildConsole switch is now supported.
  • Fixed a bug where ‘requestedPrivileges’ tag in the manifest file is embedded twice (rare scenario).
  • Fixed a bug in which the XML documentation file was not created.
  • Fixed a rare bug in which a manifest file was not added during link.
  • Fixed a bug which caused a failure during preprocessing (error: “Max. supported stack depth exceeded”).
  • Fixed a bug in which property sheet values were not analyzed correctly.
  • Fixed a bug in which division by zero assertions appeared during dependency evaluation.

Xoreax Grid Engine (XGE) Interfaces

  • cscript/JavaScript can now be distributed to 32-bit remote Agents.
  • XGConsole command line now supports double quotes.
  • Fixed a bug in which “Unexpected error: Exception: Wait State Warning (possible deadlock)” appeared.
  • Fixed a crash which occurred in ve32.bin on remote Agents.

Stability

  • Remote Agents shut down while building can no longer cause the build to fail (rare scenario).
  • Virtual address space usage exceeding the 128MB limit is now supported (would cause “shared stream group lock abandoned” errors).
  • /wait flag in BuildConsole no longer fails builds.
  • Large output buffers received from remote Agents are now supported (would cause “Not enough storage is available to process this command” errors).

User Interface

  • Added support for specifying the maximum number of cores which will link in parallel on the initiating Agent.

Virtual Environment

  • Added support for distribution of the Nvidia CUDA compiler.

(Back to top)

Changes in Version 3.60

Changes in Version 3.60 (Release Date: May 12, 2011)

Note: This list also contains changes included in Version 3.60 Beta and Version 3.60 Beta 2. For a list of differences between v3.60 and v3.60 Beta 2, see this section.

Version Highlights

  • Added support for distributed Visual Studio 2010 builds (for a list of known issues click here).
  • Added support for distributed Nintendo 3DS builds from the Visual Studio IDE (currently in Visual Studio 2008 and earlier).
  • New, faster and more accurate dependency evaluation mechanism now used in Visual Studio builds (Visual Studio 2008 and earlier).
  • Eliminated “Updating Dependencies” bar during build initialization. Dependencies are now calculated throughout the build in parallel to compilation.
  • Added new Agent scheduling feature that enables Agent automatically in pre-defined hours.
  • Added new “View Process Activity” right-click option in Build Monitor Progress view which shows output and process information for remotely run processes.
  • Added support for Intel Parallel Composer 2011.

Visual Studio Build System

  • Added support for distributed Visual Studio 2010 builds (for a list of known issues click here).
  • New, faster and more accurate dependency evaluation mechanism now used in Visual Studio builds.
  • Added support for distributed Nintendo 3DS™ builds from the Visual Studio environment (Visual Studio 2008 and earlier).
  • Added support for Intel Parallel Composer 2011.
  • Improved error message given when specified property sheet is missing.
  • Improved error message given when two or more files were configured to generate the same output file.
  • Fixed several bugs related to macro expansion.
  • Fixed several bugs related to dependencies between custom steps over several dependent projects.
  • Fixed a bug that could cause the wrong version of a referenced assembly to be chosen if more than one version is installed.
  • Fixed a bug that could cause builds to fail with a “The filename or extension is too long (206)” error.
  • Added support for /privilege command line options (Xbox).
  • Fixed a bug related to the /DYNAMICBASE linker command line option.
  • Fixed a bug related to the /GS compiler command line option.
  • Fixed a bug related to the /Qdiag-file Intel compiler command line option.
  • Fixed a bug that could cause “Cannot open source file: No such file or directory” errors for dlldata.c.
  • Fixed a bug related to property sheets specified with relative paths.
  • Fixed a bug related to the “Minimal directory synchronization” mode.
  • IB now correctly removes duplicate entries in the RC tool command line.
  • Fixed a bug that caused IncrediBuild to fail whenever the VCLinkTool element was missing from the vcproj file.
  • Fixed a bug related to trailing/leading whitespaces in property sheets and vcproj files.
  • Added support for Nintendo 3DS integration.
  • Fixed a bug in which the $(Outdir) macro was not calculated correctly.
  • Fixed a bug in the IncrediBuild preprocessor in which false conditions were not calculated correctly.
  • Fixed a bug in the IncrediBuild preprocessor in which UTF-8 encoded files were not parsed correctly.
  • Fixed a bug which caused build system failures when $(Inherit) macro was used.
  • Fixed a bug in which the wrong linkage order caused errors.
  • Fixed a bug in which /FU was not added for interop assemblies.
  • Fixed a bug which caused the wrong Intel Compiler to be used when several versions are installed on the same machine.
  • Fixed a bug which caused an increase in linkage time during the manifest step.
  • Fixed a bug in which resx files were not compiled in managed C++ projects.

Performance

  • Eliminated “Updating Dependencies” bar during build initialization. Dependencies are now calculated throughout the build in parallel to compilation.
  • The amount of directory synchronization in Automatic Interception builds is now reduced improving overall performance.

Stability

  • Termination of locally run processes in now safer.
  • Fixed a minor memory leak in both Agent and Coordinator services.
  • Fixed a memory leak that could occur when tasks write large amounts of output to stdout/stderr.
  • Fixed a memory leak in the Coordinator service.
  • Optimized handling of build events to improve general build system responsiveness.
  • Increased internal db file size limits to 6GB.
  • Fixed a bug that could result in a “Failed to assign process to job: Access is denied” error when a remote machine shuts down during build.
  • Fixed a bug that could cause a “Cannot write to a read-only mapped file” automatic recovery message.

User Interface

  • Added a new /ResetAllFileCaches command line option to xgCoordConsole which clears the file cache on all connected Agents.
  • Added a new Agent Settings option that limits the number of logical processors utilized in builds started by a specific Agent.
  • Added a new .sln file path and project name columns to Coordinator Monitor.
  • Added a new /QUERYLICENSE command line option (BuildConsole and xgConsole) which outputs the Agents’ license details.
  • xgConsole now returns proper error message when the specified profile xml filename doesn’t exist.
  • Fixed a bug in Build Monitor that sometimes caused the horizontal scroll-bar to appear slightly right-justified.
  • Maintenance expiration notice now includes the current license’s maintenance expiration date.

Virtualization

  • Added support for direct execution of .bat/.cmd files on remote machines.
  • Fixed a bug related to use of mapped drives (support was broken in v3.51).
  • Fixed a bug related to search path compatibility.
  • Fixed a bug related to execution of hostname.exe on remote machines.
  • Fixed a bug that could cause cygwin echo.exe to fail remotely.
  • Fixed a bug that could cause the g++ compiler to fail on Win7 x64 machines.
  • Fixed a bug that could cause failures when running wmake remotely.

Miscellaneous

  • xgCoordConsole XML dump now includes additional information related to Backup Coordinator identification and status, Agent assignment settings and license information.
  • Coordinator Monitor and Agent tray-icon now give a clear indication when Agent is automatically disabled due to it running on battery power or during work hours specified by the automatic scheduler.
  • Fixed a bug in xgCoordConsole that could cause it to fail whenever run from a machine without the Coordinator service.
  • Visual C++ redistributable packages are now installed in quiet mode when run through the silent installer.
  • Backup Coordinator is now updated when changing an Agent to work with a different Coordinator.

Visual Studio Integration

  • Added a clear error message which replaced the ‘Not enough storage is available’ message when building a solution which includes Intel VTune analysis folders.
  • Fixed a bug that could prevent the Intel Compiler from being recognized on Windows 7 x64 machines using UAC.
  • Fixed a bug that could prevent change of input languages in Visual Studio 6.0 when IncrediBuild is installed.
  • Fixed a bug that could prevent the Intel C++ Compiler from being recognized when non-English default locale was used.

Xoreax Grid Engine (XGE) Interfaces

  • /ShowAgent is now supported in Automatic Interception XGE builds.
  • VCCompiler Tool property now implicitly enables “Restart remote processes on local machine” property.
  • Fixed a bug related to the /setenv xgConsole command line option.
  • Fixed a bug that could cause partial output to be displayed when /StopOnErrors was used in XGE builds.
  • Fixed a bug related to use of piping.
  • Fixed a bug in which Symbian builds failed to spawn processes.

Known Issues (Visual Studio 2010)

  • Distribution of Midl steps is not supported in Visual Studio 2010 builds.
  • In certain cases where projects depend on other projects which are unloaded from the solution, dependencies may be unnecessarily rebuilt.
  • Distribution of Custom Build Steps and Build Events is not supported in Visual Studio 2010 builds.
  • Agent Settings – ‘Build Monitor | Output -> Show Command Line’ option is not supported in Visual STudio 2010 builds.
  • Solution Settings dialog IncrediBuild options are not supported in Visual STudio 2010 builds.

Differences Between v3.60 & v3.60 Beta 2

Visual Studio Build System
  • Improved and stabilized support for Visual Studio 2010.
  • Added support for distributed Nintendo 3DS builds from the Visual Studio IDE (currently in Visual Studio 2008 and earlier).
  • Fixed a bug in which the $(Outdir) macro was not calculated correctly.
  • Fixed a bug in the IncrediBuild preprocessor in which false conditions were not calculated correctly.
  • Fixed a bug in the IncrediBuild preprocessor in which UTF-8 encoded files were not parsed correctly.
  • Fixed a bug which caused unloaded projects to be built in Visual Studio 2010.
  • Fixed a bug which caused build system failures when $(Inherit) macro was used.
  • Fixed a bug in which the wrong linkage order caused errors.
  • Fixed a bug in which /FU was not added for interop assemblies.
  • Fixed a bug which caused the wrong Intel Compiler to be used when several versions are installed on the same machine.
  • Fixed a bug which caused an increase in linkage time during the manifest step.
  • Fixed a bug in which resx files were not compiled in managed C++ projects.
Visual Studio Integration
  • Added a clear error message which replaced the ‘Not enough storage is available’ message when building a solution which includes Intel VTune analysis folders.
Stability
  • Fixed a bug in which builds failed with STATUS_DLL_NOT_FOUND errors.
  • Fixed a memory leak which occurred when spawning hundreds of processes from a single process.
  • Fixed a bug which caused GetUserNameExA to fail when running in detailed logging on Windows 7 64-bit.
  • Fixed a limitation in memory allocation which caused errors when using the /Zm compiler switch with values higher than 500.
  • Increased the default Build System timeout to 40 seconds in order to support the longer initialization time required when running builds under the CruiseControl .Net service.
User Interface
  • Fixed a bug in the automatic Agent Scheduler which occurred when running in an Italian locale.
  • Fixed a bug in which CPU utilization settings were not saved during a new agent installation.
  • Fixed a bug in the Build Monitor which caused an exception when double-clicking on the red error icon.
  • Fixed a spelling mistake in “Building list of agents to roll back…” message.
  • Enlarged the size of the Agent Assignment combobox which can now support up to 32000 agents.
  • Removed ‘Optimize Project Build Order’ option from the agent settings since it is no longer relevant.
Virtualization
  • Added support for the GetVolumeInformation Win32API function on remote agents.
Xoreax Grid Engine (XGE) Interfaces
  • Fixed a bug in which Symbian builds failed to spawn processes.

(Back to top)

Changes in Version 3.60 Beta 2

Changes in Version 3.60 Beta 2 (Release Date: January 31, 2011)

New Features

  • Added support for distributed Visual Studio 2010 builds.
  • Added new Agent scheduling feature that enables Agent automatically in pre-defined hours.
  • Added new “View Process Activity” right-click option in Build Monitor Progress view which shows output and process information for remotely run processes.

Miscellaneous

  • xgCoordConsole XML dump now includes additional information related to Backup Coordinator identification and status, Agent assignment settings and license information.
  • Coordinator Monitor and Agent tray-icon now give a clear indication when Agent is automatically disabled due to it running on battery power or during work hours specified by the automatic scheduler.
  • Fixed a bug in xgCoordConsole that could cause it to fail whenever run from a machine without the Coordinator service.
  • Visual C++ redistributable packages are now installed in quiet mode when run through the silent installer.

Visual Studio Build System

  • Added support for distributed Visual Studio 2010 builds.
  • Added support for Intel Parallel Composer 2011.
  • Fixed a bug in v3.60 beta which caused incorrect compilation order in managed projects using Forced Using statements.
  • Fixed a bug in v3.60 Beta which caused /Compile BuildConsole option to fail when filenames included a space character.
  • Fixed a bug in v3.60 Beta which caused builds to fail if project files were saved in Unicode format.
  • Fixed a bug in v3.60 Beta which caused builds to fail whenever two or more source files with the same name existed in the project.
  • Fixed a bug in v3.60 Beta which caused builds to fail whenever the project filename contained a “-” character.
  • Fixed a bug in v3.60 Beta related to the use of $(Inherit) macro.
  • Fixed a bug in v3.60 Beta that could cause linker errors in x64 builds.
  • Fixed several bugs in v3.60 Beta dependency evaluation mechanism.
  • Improved error message given when specified property sheet is missing.
  • Improved error message given when two or more files were configured to generate the same output file.

Stability

  • Termination of locally run processes in now safer.

(Back to top)

Changes in Version 3.60 Beta

Changes in Version 3.60 Beta (Release Date: October 29, 2010)

Performance

  • Eliminated “Updating Dependencies” bar during build initialization. Dependencies are now calculated throughout the build in parallel to compilation.
  • The amount of directory synchronization in Automatic Interception builds is now reduced improving overall performance.

Stability

  • Fixed a minor memory leak in both Agent and Coordinator services.
  • Fixed a memory leak that could occur when tasks write large amounts of output to stdout/stderr.
  • Fixed a memory leak in the Coordinator service.
  • Optimized handling of build events to improve general build system responsiveness.
  • Increased internal db file size limits to 6GB.
  • Fixed a bug that could result in a “Failed to assign process to job: Access is denied” error when a remote machine shuts down during build.
  • Fixed a bug that could cause a “Cannot write to a read-only mapped file” automatic recovery message.

User Interface

  • Added a new /ResetAllFileCaches command line option to xgCoordConsole which clears the file cache on all connected Agents.
  • Added a new Agent Settings option that limits the number of logical processors utilized in builds started by a specific Agent.
  • Added a new .sln file path and project name columns to Coordinator Monitor.
  • Added a new /QUERYLICENSE command line option (BuildConsole and xgConsole) which outputs the Agents’ license details.
  • xgConsole now returns proper error message when the specified profile xml filename doesn’t exist.
  • Fixed a bug in Build Monitor that sometimes caused the horizontal scroll-bar to appear slightly right-justified.
  • Maintenance expiration notice now includes the current license’s maintenance expiration date.

Virtualization

  • Fixed a bug related to use of mapped drives (support was broken in v3.51).
  • Fixed a bug related to search path compatibility.
  • Fixed a bug related to execution of hostname.exe on remote machines.
  • Added support for direct execution of .bat/.cmd files on remote machines.
  • Fixed a bug that could cause cygwin echo.exe to fail remotely.
  • Fixed a bug that could cause the g++ compiler to fail on Win7 x64 machines.
  • Fixed a bug that could cause failures when running wmake remotely.

Visual Studio Build System

  • New, faster and more accurate dependency evaluation mechanism now used in Visual Studio builds.
  • Fixed several bugs related to macro expansion.
  • Fixed several bugs related to dependencies between custom steps over several dependent projects.
  • Fixed a bug that could cause the wrong version of a referenced assembly to be chosen if more than one version is installed.
  • Fixed a bug that could cause builds to fail with a “The filename or extension is too long (206)” error.
  • Added support for /privilege command line options (Xbox).
  • Fixed a bug related to the /DYNAMICBASE linker command line option.
  • Fixed a bug related to the /GS compiler command line option.
  • Fixed a bug related to the /Qdiag-file Intel compiler command line option.
  • Fixed a bug that could cause “Cannot open source file: No such file or directory” errors for dlldata.c.
  • Fixed a bug related to property sheets specified with relative paths.
  • Fixed a bug related to the “Minimal directory synchronization” mode.
  • IB now correctly removes duplicate entries in the RC tool command line.
  • Fixed a bug that caused IncrediBuild to fail whenever the VCLinkTool element was missing from the vcproj file.
  • Fixed a bug related to trailing/leading whitespaces in property sheets and vcproj files.

Visual Studio Integration

  • Fixed a bug that could prevent the Intel Compiler from being recognized on Windows 7 x64 machines using UAC.
  • Fixed a bug that could prevent change of input languages in Visual Studio 6.0 when IncrediBuild is installed.
  • Fixed a bug that could prevent the Intel C++ Compiler from being recognized when non-English default locale was used.

Xoreax Grid Engine (XGE) Interfaces

  • /ShowAgent is now supported in Automatic Interception XGE builds.
  • VCCompiler Tool property now implicitly enables “Restart remote processes on local machine” property.
  • Fixed a bug related to the /setenv xgConsole command line option.
  • Fixed a bug that could cause partial output to be displayed when /StopOnErrors was used in XGE builds.
  • Fixed a bug related to use of piping.

Miscellaneous

  • Backup Coordinator is now updated when changing an Agent to work with a different Coordinator.

(Back to top)

Changes in Version 3.51

Changes in Version 3.51 (Release Date: March 7, 2010)

Visual Studio Build System

  • Fixed a bug that caused non-standard (e.g. third-party) project files not to be recognized in builds started from the Visual Studio IDE.
  • Fixed a bug that could cause files generated by midl steps (e.g. dlldata.c) to be incorrectly reported as not found.
  • Fixed a bug that caused errors when running BuildConsole.exe with response (.rsp) files as input.
  • Fixed a bug that caused builds to fail whenever a referenced C# project uses a non-default BaseIntermediateOutputPath specification.
  • Fixed a rare bug that could result in builds failing with a “Fatal error C1859” message.
  • Fixed a bug that could cause failed custom rule tasks to be reported as successful.
  • Fixed a bug that could cause incorrect compiler command lines to be used for smart device target platform builds.
  • Fixed a bug related to custom rule properties accepting multiple values.
  • Fixed a rare bug related to non-standard values specified in the “Use of MFC” Project property.
  • Fixed a warning related to the /INCREMENTAL linker option in the 11164 Xbox 360 XDK.

Performance

  • Fixed a bug that could cause a delay in build startup on Windows 7 and Vista machines.
  • Improved performance of writing the build progress file (.ib_mon) to disk.
  • Added various internal performance optimizations.

User Interface

  • Build History application now opens with the same view filters that were active the last time it was closed.

Stability

  • Fixed a bug that could prevent Agents from connecting to the Coordinator after an upgrade to v3.5.

Virtualization

  • Fixed a bug that could result in incorrect identification of removable drives as fixed (could affect build performance).

Xoreax Grid Engine (XGE) Interfaces

  • Termination of intercepted processes (via the Automatic Interception interface) is now cleaner.
  • Fixed a bug that prevented Automatic Interception builds from running when the /SHOWTIME command line option was specified.

Miscellaneous

  • Remote execution on Windows 2000 machines is no longer supported (initiation of builds from Windows 2000 machines is supported).
  • Added /LOGLEVEL command line option (xgConsole/BuildConsole) which overrides the current logging level.
  • Fixed a bug that prevented version rollbacks from working whenever the “Update version of all subscribed Agents automatically” option was selected.
  • Fixed a bug that caused Agents to keep working with the old Backup Coordinator after changing to a new Primary Coordinator.
  • Fixed a bug that could prevent the Coordinator service from starting on machines that changed certain locale settings.

(Back to top)