Builds Executed

The total number of builds executed using IncrediBuild.

Build Status

Successful - The number of builds successfully completed by IncrediBuild. 
Failed - The number of builds that were initiated using IncrediBuild that were not completed successfully. This number includes Builds that failed to execute, as well as builds that were aborted by the system or by the user.

Avg. Build Duration

The average time that it took to execute each build using IncrediBuild.

Distributed [%]

The percentage of the total time that tasks were executed remotely versus the total time tasks were executed both remotely and locally - a higher number means better distribution. This value is calculated by taking the total duration of builds all the tasks that were executed on remote agents Agents cores and dividing it by the total duration of builds all the tasks executed on all agents Agents, both remote and local cores. (including local agents). For example: if a build was executed on the local agent Agent as well as 9 remote agents Agents cores and the execution of each task lasted for lasted  one hour, then we divide the 9 hours of execution on remote agents Agents cores by the total of 10 hours of execution which would yield the result of 90% build tasks distribution.The percentage of the tasks executed with IncrediBuild that were executed on remote agents. This value is calculated by taking the number of core-hours of execution on remote cores and dividing it by the total number of core-hours of execution on all cores (including the local cores). For example, if a build was executed on the local agent, which has one core, as well as on 9 remote cores and the execution took one hour, then we divide the 9 core-hours of execution on remote cores by the total of 10 core-hours of execution which yields the result of 90% Distributed execution.This is not accurate. This value is the sum of the duration of all tasks executed remotely divided by the sum of all the tasks executed both remotely and locally. Talk to me if this is not clear. For example, if a build consists of 16 tasks each taking 1 minute, 4 of them were executed locally and 12 were executed remotely, the value will be 12/16=75% All of the revisions are making this definition too complex. I started from scratch and wrote a straight forward definition, using the concept of core-hours that I introduced above. 90%  tasks distribution.

Note: The more that you are able to utilize remote cores to decrease the workload on the local agent Agent the greater the benefit you are obtaining from IncrediBuild. So, a high Distributed Percentage percentage indicates an effective use of the toolIncrediBuild infrastructure.

Agent Name

The name of the initiator agentAgent.

Status

The status of a build is either Success or Failed. 
Success - The build was completed successfully. 
Failed - The builds was not completed successfully. The failure could result from a failure of the system to execute the build of from the execution being aborted by the system or by the user.

Duration

The time that it took to execute the build.

Should this be Distributed [%]?{*}Distributed [%]*Yes, and it was changed in the UI

The percentage of the build that was executed using remote agents Agents (i.e. Helpers) as opposed to the local agentAgent (i,e, Initiator). This value is calculated by taking the total duration of the build executed on remote agents Agents and dividing it by the total duration of builds executed on all agents Agents (including the local agentAgent). For example: if a build was executed on the local agent Agent as well as 9 remote agents Agents and the execution lasted for one hour, then we divide the 9 hours of execution on remote agents Agents by the total of 10 hours of execution which would yield the result of 90% build distribution.The explanation is not accurate in the same manner as above The percentage of the tasks executed with IncrediBuild that were executed on remote agentsAgents. This value is calculated by taking the number of core-hours of execution on remote cores and dividing it by the total number of core-hours of execution on all cores (including the local cores). For example, if a build was executed on the local agentAgent, which has one core, as well as on 9 remote cores and the execution took one hour, then we divide the 9 core-hours of execution on remote cores by the total of 10 core-hours of execution which yields the result of 90% Distributed execution. 

Avg. Additional Cores Needed

This value indicates the average number of additional cores (beyond the number of cores that were available) that could have been used to execute the build. During a build's execution, the system registers a value every second for the number of additional cores needed. Therefore, this value is determined by taking the aggregate of the number of cores needed for each second and dividing the sum by the number of seconds that the build was executed. For example, a value of '0' indicates that adding more cores to the deployment would not improve the efficiency of the build. A higher value indicates that adding additional cores could potentially increase the performance of the build.

Peak Additional Cores Needed

The highest value registered for additional cores needed at any point during the build.

Time Saved

This is a rough estimate of how much longer it would have taken to run this build if it was executed entirely on the initiator agentAgent. The calculation is made by taking the aggregate of the core-hours (a core-hour is an hour of utilization of each core, i.e. a 4 core machine running for one hour would be considered to have utilized four core-hours) of utilization of all remote (i.e. helper) agents Agents and dividing that by the number of cores on the local agentAgent. Since usage of the remote agents Agents is less efficient than usage of the initiator agent Agent (because of I/O and Network factors etc.), the result is divided in halfby half by 1.5. For example, if the initiator agent Agent has 4 cores and the build ran for an hour using an additional 12 cores on remote agentsAgents. Then we take the 12 core-hours and divide that by the 4 cores on the initiator agent Agent which yields the result of 3 hours. We then take that number and divide it in halfby by a factor of 1.5 to reach the result that the Time Saved was 1.52 2 hours. 
Since this calculation is based on a series of assumptions and approximations the result should be viewed as a rough estimate of the actual time saved.

Avoid Local

This is a Boolean field that was set by the user who initiated the build. 
TrueYes – Every task that can be executed remotely is done remotely and not on the local agentAgent. 
FalseNo – Tasks that can be distributed are permitted to run both on local and remote cores as determined by IncrediBuild.

Start Time

The date and time that the build execution began.

End Time

The date and time that the build execution was completed.

Avg Used Cores

The average number of cores used at a given point in time during the build execution. The number of cores being used is registered for every second. Therefore, this value is determined by taking the aggregate of the number of cores being used for each second and dividing the sum by the number of seconds that the build was executed.

Product

If a specific product or products are associated with the build command, then the product name/s are displayed.

Command

The complete command line that was used to execute the build.

Build Caption

This is a string expression that represents a specific build execution. This can be user-defined or automatically generated. It may incorporate the name of the solution for which the build was executed. If the build was executed through the command line and the Title command argument wasn't specified then no Build Caption is applied and this field remains empty.

Status

The status of a build is either Success or Failed. 
Success - The build was completed successfully. 
Failed - The build was not completed successfully. The failure could result from a failure of the system to execute the build or from the execution being aborted by the system or by the user.

Start Time

The time at which the build began execution.

Duration

The duration of time that it took to execute the build.

Initiator

The name of the initiator agentAgent.

Distributed

The percentage of the build that was executed using remote agents Agents (i.e. Helpers) as opposed to the local agentAgent (i.e. Initiator). This value is calculated by taking the total duration of the build executed on remote agents Agents and dividing it by the total duration of builds executed on all agents Agents (including the local agentAgent). For example: if a build was executed on the local agent Agent as well as 9 remote agents Agents and the execution lasted for one hour, then we divide the 9 hours of execution on remote agents Agents by the total of 10 hours of execution which would yield the result of 90% build distribution.Same comment as above The percentage of the tasks executed with IncrediBuild that were executed on remote agentsAgents. This value is calculated by taking the number of core-hours of execution on remote cores and dividing it by the total number of core-hours of execution on all cores (including the local cores). For example, if a build was executed on the local agentAgent, which has one core, as well as on 9 remote cores and the execution took one hour, then we divide the 9 core-hours of execution on remote cores by the total of 10 core-hours of execution which yields the result of 90% Distributed execution. 

Avg. Cores Used

The average number of cores used at a given point in time during the build execution. The number of cores being used is registered for every second. Therefore, this value is determined by taking the aggregate of the number of cores being used for each second and dividing the sum by the number of seconds that the build was executed.

Build Command

This is the command line with which the build was executed. Because it is a long string it is not displayed in the grid. The word 'show' is displayed for all entries in this column. Hovering over 'show' for a specific build generates a pop-out window with the full Build Command string.

Build Type

The type of build that was executed. The following are the possible Build types: 

• Build - An Incremental build operation of a Visual Studio solution or project/s. 
• Clean - A clean build operation of a Visual Studio solution or project/s. 
• Rebuild - A full rebuild operation, which consists of Clean and Build operations of a Visual Studio solution or project/s. 
• Unknown - Other IncrediBuild executions which are not Visual Studio compilations. 
  Note: Specific Build Types are registered for Visual Studio builds which are executed through the IDE or the IncrediBuild BuildConsole. All other builds or executions are registered as Unknown.

Estimated Time Saved

This is a rough estimate of how much longer it would have taken to run this build if it was executed entirely on the initiator agent Agent . The calculation is made by taking the aggregate of the core-hours (a core-hour is an hour of utilization of each core, i.e. a 4 core machine running for one hour would be considered to have utilized four core-hours) of utilization of all remote (i.e. helper) agents Agents and dividing that by the number of cores on the local agentAgent. Since usage of the remote agents Agents is less efficient than usage of the initiator agent Agent (because of I/O and Network factors etc.), the result is divided in halfby by a factor of 1.5. For example, if the initiator agent Agent has 4 cores and the build ran for an hour using an additional 12 cores on remote agentsAgents. Then we take the 12 core-hours and divide that by the 4 cores on the initiator agent Agent which yields the result of 3 hours. We then take that number and divide it by a factor of 1.5in half 5 to reach the result that the Time Saved was 1.52 2 hours. 
Since this calculation is based on a series of assumptions and approximations the result should be viewed as a rough estimate of the actual time saved.

End Time

The time that the build was completed.

Avg. Additional Cores Needed

This value indicates the average number of additional cores (beyond the number of cores that are currently available) that could have been used to execute the build. The system registers a value every second for the number of additional cores needed, so that this value is determined by taking the aggregate of the number of cores needed for each second and dividing the sum by the number of seconds that the build was executed. For example, a value of '0' indicates that adding more cores to the deployment would not improve the efficiency of the build. A higher value indicates that adding additional cores could potentially increase the efficiency of the build.

Peak Cores Needed

The highest value registered for additional cores needed at any point during the build.

Peak Cores Used

The highest number of cores that were used simultaneously at any point during the build.

Avoid Local

This is a Boolean field that was set by the user who initiated the build. 
True – Every task that can be executed remotely is done executed remotely if possible and not on the local agentAgent. 
False – All Ttasks – Tasks that can be distributedexecuted distributed are permitted to run both to on the local and remote agents cores as determined by IncrediBuild.Tasks can be distributed both to the local and remote agents as determined by IncrediBuild.Same correction as aboveMade a change to the wording, as we use the term "distributed" only to tasks that were executed remotely 

Product

If a specific product or products areOr products are associated with the build command, then the product name/s is displayed.