What’s New in Automated Build Studio 4.10
More about Build Studio
What's New in Version 4
Screencasts
Support & Resources
New Features
The Script Editor has been improved. Now, when a script that contains calls to other operations is
being executed in the editor, the editor’s Log panel displays the operation’s details and results.
The behavior of Perforce operations has been corrected. Now, when an operation
that belongs to this category reports the “file(s) up-to-date” error, the operation is still considered successful.
The output made by the Run MSTest operation now contains a detailed list of failed tests when a failure occurs.
For each operation, there was a special test that checked whether the software
needed for operations is installed on the local computer. However, the child operations of
the Remote Group and Remote Execution Stack operations are
supposed to be launched on a remote computer, so, software verification for these operations was
useless and only increased the macro execution time. In version 4.10, software verification is not performed for child operations of
the Remote Group and Remote Execution Stack operations.
The InstallShield 7-2008 and InstallShield Standalone Build operations have a new Additional Options property that lets you specify additional settings for building your projects.
Bug Fixes
Now, the working folder where the solution file resides is set as the working
folder of the Compile Visual Studio Solution operation.
The error that occurred in EurekaLog operations during the package compilation has
been fixed.
The Get File(s) From TFVC operation could retrieve the same files several times.
If the Output to file parameter was not specified for the Run NUnit Test operation, Build Studio created
the log file in the <Automated Build Studio>\Bin folder. Now, Build Studio creates the log file in the folder where the tested assembly or NUnit project resides.
The errors that occurred in the Compile Delphi 2007 for Win32 Project operation
have been fixed.
If an operation’s description contained a variable, Build Studio posted the variable name along with the description text to the Summary panel. Now the variable name is replaced with the actual value of the variable.
An error that occurred in the Wait for Window operation has been fixed.
The TestComplete and TestExecute operations generated incorrect results if an error occurred while TestComplete or TestExecute was loading.
It was impossible to use a variable in the Assigned To field of the AQdevTeam Create Issue operation.
Errors that occurred in the Surround SCM Label operation have been fixed.
The operations of the JediVCS category could handle a limited number of projects.
If the MSI file parameter was empty, the Advanced Installer operation created an installation package in the same folder where
the Advanced Installer project file resided. Now, in this situation, MSI packages are created in the folder specified by the Advanced Installer project.
The compilation log of Microsoft Visual Studio projects was parsed incorrectly.


