Versions Compared

Old Version 1

changes.mady.by.user IncrediBuild

Saved on Mar 15, 2018

compared with

New Version 2

changes.mady.by.user Idan Eldar

Saved on Apr 22, 2018

• Next Change: Difference between versions 2 and 3
• View Page History

Key

• This line was added.
• This line was removed.
• Formatting was changed.

 

Description

項目は次の通りです。

Section

The total number of builds executed using IncrediBuild. Column Builds PageThe Builds page shows information about the builds executed using IncrediBuild (In this document and in the dashboard terminology, a build refers to any execution that was executed with IncrediBuild and not only compilations). This includes both general information about build execution across your entire deployment as well as specific information about specific builds and executing Agents (i.e. Initiators). You can set filters to specify the parameters for the data represented and displayed on this page.  On this page ページ 「Builds」ページではデプロイメント全体のビルド情報だけでなく、特定のビルドや Agent (イニシエーター) の実行に関する情報など IncrediBuild で行われたビルド*のさまざまな詳細をご覧になれます。このページに表示される値はフィルターを使って絞り込むことができます。 *この資料とダッシュボードでは「ビルド」とはコンパイルだけでなく、IncrediBuild で行われたすべての処理を指します。  メニュー: To set a custom time range: Table of Content Zone location top Filters Filters allow you to set the parameters for the data that is represented on the Builds page.  フィルター 「Builds」ページに表示するデータを絞り込むことができます。 Panel borderColor black borderWidth 1 borderStyle dashed Note: All measures displayed on this page represent only to the data within the parameters set from the build Filters. Page Header Image Removed In the Page Header, below "Builds Overview", the Valid For information is displayed. This shows the date and time that the data represented on this page was last refreshed. This is considered to be the current time regarding the time filters set for the page. The data refreshes automatically every hour, assuming that the Time Filter is set for a time range that is dependent on the current time. 注意: ビルド フィルターで設定した値のみが表示されます。 ページ ヘッダー Image Added ページ左上の「Build Overview」下の [Valid For] でデータの最終更新日時を確認できます。ここに表示される日時がページ内でタイムフィルターを適用する際の現在時刻となります。データは 1 時間ごとに自動的に更新されます。タイム フィルターで設定されるタイムレンジは現在時刻に基づきます。  The preset time ranges are described in the following table: Panel borderColor black borderWidth 1 borderStyle dashed Note: You can update the current time manually by refreshing the page. However, refreshing the page will also reset any filters that you have set and return them to their default settings. Time Filter The Time filter enables you to filter the data represented on the Builds page to include only builds run during the specified time period.  Image Removed You can set the time filter using one of the preset time range buttons or you can create a custom time range. 注意: ページを再読み込みすると現在時刻を手動で更新できます。この場合、設定済みのフィルターはリセットされます。 タイムフィルター 指定期間のデータのみを絞り込んで表示できます。  Image Added プリセットまたはカスタムのタイムレンジを作成して適用します。 プリセットのタイムレンジは下表の通りです。 Click on Custom in the Page Header filter pane. Panel borderColor black borderWidth 1 borderStyle dashed Note: In the descriptions below, the Current time refers to the time that the data on the page was last refreshed. Category Description 12H Includes data from builds executed in the 12 hours prior to the current time. 24H Includes data from builds executed in the 24 hours prior to the current time. This is the default selection. Today Includes data from builds executed from 00:00 of the current day up to the current time. 注意: 以下の説明ではデータの最終更新日時を現在時刻としています。 項目 説明 12H 現在時刻から 12 時間前までに実行されたビルドのデータを表示します。 24H 現在時刻から 24 時間前までに実行されたビルドのデータを表示します。デフォルトで選択されています。 Today 当日 00:00 から現在時刻までに実行されたビルドのデータを表示します。 タイムレンジを自分で設定する方法 ページ ヘッダーで [Custom] をクリックします。       2.[Pick a Date Range window is displayed:  Range] 画面が表示されます。      Image Modified Click OK.         3. Click on the From Date field. Image Removed A calendar selection window is displayed. Select a date. The default is set for the current date. To select a date from a previous month, click the back arrow on the top of the calendar and then select a date. [From Date] をクリックします。         Image Added カレンダーが表示されます。 日付を選択します。 デフォルトで当日が選択されています。 前の月に移動するにはカレンダー上部の左向き矢印をクリックします。 [OK] をクリックします。       4. Do the same for the end date. Product Filter The Product filter enables you to filter the data represented on this page to include only builds associated with a specific product (or products). The product profiles must first be created in the Products Configuration page before they can be applied to the Builds page . . To set the Product filter: Click on the Product field. A multi-select list of products is displayed: Image Removed Click the checkbox next to each of the products to be included.[To Date] フィールドも同様に選択します。 プロダクト フィルター 特定のプロダクトに関連するビルドを絞り込んで表示できます。フィルターを適用する前に「Configuration」ページの「Product 設定 」タブでプロダクトのプロフィールを作成する必要があります。 . プロダクト フィルターの設定方法 [Products] フィールドをクリックします。 プロダクトが一覧表示されます。 Image Added 表示したいプロダクトの横にあるチェックボックスをオンにします。 Notes: Once this filter is applied, the filter will be marked. The default value is set to include all build commands regardless of products.  If no products have been created an option to Add Products is displayed in the Product filter drop down menu. Panel borderColor black borderWidth 1 borderStyle dashed Build Types Filter The Build Types filter enables you to filter the data represented on the Builds page to include only builds of a specified type. You can select one or more Build Types to be included in the data displayed. 注意: フィルターが適用されると [Product] フィールドに赤字でプロダクト名が表示されます。 デフォルトではビルドコマンドによる絞り込みなしで、すべてのビルドが表示されます。  プロダクトを未作成の場合は [Add Products] オプションがドロップダウン メニューに表示されます。 ビルドタイプ フィルター 特定タイプのビルドを絞り込んで表示できます。ビルドタイプは複数選択できます。 Note: Specific Build Types are registered for Visual Studio builds which are executed through the IDE or the IncrediBuild BuildConsole command line. All other builds or other executions are registered as Unknown. Panel borderColor black borderWidth 1 borderStyle dashed The Build Types are described in the following table: 注意: IDE または IncrediBuild BuildConsole コマンドラインで実行される Visual Studio ビルドのみがビルドタイプに登録されています。その他のビルドや処理は「Unknown」として表示されます ビルドタイプは下表の通りです。 The filter is applied. The selected Build Types are shown on the display. Category Description 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. To set the Build Types filter: Click on the Build Types field from the Page Header filters pane. A multi-select list of the Build Types is displayed. Image Removed Click the checkbox next to each of the Build Types to be included. Visual Studio ソリューションまたはプロジェクトのリビルド (クリーンしてからビルド)。 Unknown Visual Studio コンパイルを除く IncrediBuild の処理。 ビルドタイプの設定方法 ページ ヘッダーの [Build Type] フィールドをクリックします。 ビルドタイプが一覧表示されます。 Image Added 表示したいビルドタイプの横にあるチェックボックスをオンにします。 選択したビルドタイプが表示されます。 Panel borderColor black borderWidth 1 borderStyle dashed Note注意: The default is set to display all Build Types.デフォルトではすべてのビルドタイプが表示されます。 Anchor BuildsKPI BuildsKPI Builds ビルド KPI Summary サマリー The Builds KPI Summary shows aggregated statistics for the KPI measures related to build usage of the IncrediBuild Infrastructure.ヘッダー下のビルド KPI サマリーには IncrediBuild システムで行われたビルドの KPI 値の統計が表示されます。 Panel borderColor black borderWidth 1 borderStyle dashed Notes 注意:  All data represented on the Builds page, including the KPI Summary are based on the parameters set in the Builds filters.  That means that data for a build is only represented in the measures on this page if the build was run during the selected time period, was related to the selected Product type, was of the selected build type and was initiated by the selected Initiator Group. The information displayed in the KPI Display is explained in the following table: Category Description Builds Executed ページ内のすべてのデータ (KPI サマリーを含む) はビルド フィルターで絞り込んだ値に基づいています。  選択した期間 / プロダクト タイプ / ビルド タイプで、選択した Agent グループによって開始されたビルドのみが表示されます。 KPI サマリーには次の情報が表示されます。 カテゴリー 説明 Builds Executed IncrediBuild で実行されたビルドの合計数。 Build Status Successful - The number of builds successfully completed by IncrediBuild.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.IncrediBuild によって実行され、失敗したビルド数。システムやユーザーによって中止されたビルドが含まれます。 Avg. Build Duration The average time that it took to execute each build using IncrediBuild.IncrediBuild で実行した各ビルドの平均所要時間。 Distributed [%]The percentage of the total time were executed remotelybuilds execution that was done on remote as opposed to local Agents. This value is calculated by taking the total duration of builds all executed on remote Agents cores and dividing it by the total duration of builds executed on all Agents remote and local cores.(including local Agents). For example: if a build was executed on the local Agent as well as 9 remote Agents cores and the execution of each task lasted for one hour, then we divide the 9 hours of execution on remote 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.  Note: The more that you are able to utilize remote cores to decrease the workload on the local Agent the greater the benefit you are obtaining from IncrediBuild. So, a high Distributed Percentage indicates an effective use of the tool. Builds Execution Over Time Graphic Display This area shows a graphic representation of the Builds KPIs over time. In the top graph you can select to display either Successful vs. Failed builds over time or Build Types over time (Default: displays Success vs. Fail graph). The lower graph shows the Distributed percentage over time (for an explanation of this measure see Builds KPI Summary). The data displayed for a given point in time relates to all builds which began execution during the time period between the last aggregation of data and the specified time.   The data shown in the graph is aggregated hourly for the last two weeks and daily for earlier dates. The legend indicating the color of the display for each element is shown at the top of the graph.  You can interact with the display in the following manner: Select/Deselect – Click on one of the data elements in the legend to show/hide that element in the display. The default is to display all elements. Therefore, the first time that you click on an element it will hide it. 合計時間に対するローカル Agent とリモート Agent で行われた処理の割合。この値はリモート Agent コアで実行したビルドの合計時間を、すべての Agent (ローカルとリモート) で実行したビルドの合計時間で割って計算します。たとえば、ローカル Agent と 9 台のリモート Agent でビルドを 1 時間行った場合、リモート Agent コアで行った処理の合計時間 (9 時間) をビルドの合計時間 (10 時間) で割って、分散処理されたタスクの割合 (90%) を計算します。  注意: リモート コアを使用するとローカル Agent の負荷が軽減されます。そのため、分散処理の割合が大きいほど IncrediBuild を効果的に利用できていることを示しています。 Builds Execution Over Time ディスプレイ このセクションでは時間の経過に伴うビルドの KPI の推移をグラフで確認できます。グラフは上下に分かれており、上のグラフでは時間の経過に伴う「成功したビルドと失敗したビルド (Success vs Fail)」または「ビルドタイプ (Build Type)」を選択できます。デフォルトでは「成功したビルドと失敗したビルド」のグラフが選択されています。下のグラフでは時間の経過に伴う分散処理の割合の推移を確認できます (表示項目の詳細は「ビルド KPI サマリー」を参照)。データが最後に集計されてから指定した時間までのすべてのビルドに関するデータが表示されます。   グラフには過去 2 週間 (毎時) とそれ以前 (毎日) の集計データが表示されます。 グラフの上部に表示項目と表示色の凡例が表示されます。  次の方法で表示を変更することができます。 表示 / 非表示 - 凡例のデータ項目をクリックするとグラフを表示 / 非表示できます。デフォルトではすべてが表示されているため、項目をクリックすると非表示になります。 Panel borderColor black borderWidth 1 borderStyle dashed Note: If a Build Type has been excluded by a filter then data for that Build Type will not be displayed even if it has been selected in the legend. Display data – Hover over a point in the graph to create a pop-out display of the specified date and time and the data for that particular point in time. 注意: フィルターで除外されているビルドタイプのデータは凡例をクリックしても表示されません。 データ表示 - グラフの任意の場所にカーソルを合わせると、その地点の日時とデータがポップアップ表示されます。 Panel borderColor black borderWidth 1 borderStyle dashed Note: The graphs are linked so that hovering over a point in one graph creates a pop-out display of data also in the second graph. Zooming – Drag the cursor over a section of the timeline to zoom in on that time range and display a more granular breakdown of the data over a shorter period of time. To return to the display of the full timeline, click the Reset Zoom button in the top right corner of the graph. 注意: 上下のグラフはリンクしています。上のグラフで任意の時点にカーソルを合わせると、下のグラフにもデータがポップアップ表示されます。 ズーム - タイムライン上でドラッグした範囲を拡大表示して、すばやくデータの詳細を表示できます。タイムライン全体の表示に戻るには、グラフ右上の [Reset Zoom] ボタンをクリックします。 This section shows two bar charts representing either the top or bottom Agents for each of the two measures Time Spent Building and # Builds Executed. You can select the parameters for the data displayed in these charts using the Build Filters. Underneath the title of each chart there is a legend indicating the color of the display for each Agent. Agent Number Filter You can select the number of Agents displayed from the dropdown list for the Agent Number Filter (options are: 5,10 or 20) from the filter pane. You can also select whether to display the Agents with the top performance or the Agents with the bottom (lowest) performance. このセクションでは 2 つの評価 (「ビルドの所要時間」と「処理したビルド数」) から上位または下位の Agent を棒グラフで確認できます。ビルド フィルターで設定したデータが表示されます。それぞれのグラフの上部に表示項目と表示色の凡例が表示されます。 Agent 表示数フィルター ドロップダウン リストから表示する Agent の数を選択できます (5、10、20 のいずれか)。また、パフォーマンス上位 (Top Initiators) または下位 (Bottom Initiators) のどちらを表示するかを選択できます。 Image Modified Time Spent Building This measure shows the aggregate of the duration of all builds initiated by a particular Agent. Either the top or bottom Agents are illustrated on the display based on your selection. The legend shows the names of the Agents and the number of hours.  You can interact with the display in the following manner: Select/Deselect – Click on one of the Agent names in the legend to show/hide that Agent for display. The default is to display all Agents. Therefore, the first time that you click on an Agent it will hide it. Display data – Hover over the bar of an Agent to create a pop-out display. The display includes: the name of the Agent, the percentage of time spent building in relation to the total time that the Agent was connected to the Coordinator and the total duration of time spent building. Number of Builds Executed This measure shows the total number of builds initiated by a particular initiator Agent (both successful and failed builds are included in this measure). Either the top or bottom Agents are displayed depending on your selection The legend shows the names of the Agents and the number of builds. このセクションでは任意の Agent が開始したすべてのビルドの総所要時間を確認できます。上位または下位いずれかの Agent を表示できます。 グラフには Agent の名前と時間が表示されます。  次の方法で表示を変更することができます。 表示 / 非表示 - 凡例の Agent 名をクリックするとグラフを表示 / 非表示できます。デフォルトではすべての Agent が表示されているため、項目をクリックすると非表示になります。 データ表示 - 各 Agent の棒グラフにカーソルを合わせると詳細データがポップアップで表示されます。Agent 名、Agent が Coordinator に接続されていた合計時間に対するビルド時間の割合、ビルドの総所要時間などが表示されます。 Number of Builds Executed このセクションでは任意のイニシエーター Agent によって開始されたビルドの総数 (成功、失敗をともに含む) を確認できます。上位または下位の Agent を表示できます。グラフには Agent 名とビルド数が表示されます。  Panel borderStyle dashed Note: This chart relates only to the number of builds and not to their duration. Therefore, the list of Agents shown and the order in which they appear will not necessarily be the same as in the Time Spent Building chart. You can interact with the display in the following manner: Select/Deselect – Click on Fail or Success in the legend to show/hide that element for display. The default is to display both successful and failed builds. Display data – Hover over the bar of an Agent to create a pop-out display of the name of the Agent together with the total number of builds, the number of successful builds and the number of failed builds. 注意: グラフはビルド数のみを表し、ビルド時間は除外されているため、ここに表示される Agent のリストおよび順序は前述の「Time Spent Building」のグラフと必ずしも同じとは限りません。 次の方法で表示を変更することができます。 表示 / 非表示 - 凡例の Fail または Success をクリックするとグラフを表示 / 非表示できます。デフォルトでは成功したビルドと失敗したビルドの両方が表示されます。 データ表示 - 各 Agent の棒グラフにカーソルを合わせるとビルドの総数、成功 / 失敗したビルド数がポップアップで表示されます。 Anchor 5longest 5longest 5 Longest Builds Display ディスプレイ This pane shows the 5 individual build executions that had the longest durations. Clicking on one of the builds displays a window with detailed information about that particular build. このセクションでは処理に時間のかかった上位 5 つのビルドを確認できます。棒グラフ下の矢印アイコンをクリックするとビルドの詳細情報が表示されます。  The parameters displayed in this window are described in the following table:

Item

アイテム	説明
Agent NameThe name	of the initiator Agent.イニシエーター Agent の名前。
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.失敗したビルド。システムやユーザーがビルドを中止したことで、システムが処理を継続できなくなったビルド。
Duration	ビルドの所要時間。
Distributed [%]The percentage of the build that was executed using remote Agents (i.e. Helpers) as opposed to the local Agent (i,e, Initiator). This value is calculated by taking the total duration of the build executed on remote Agents and dividing it by the total duration of builds executed on all Agents (including the local Agent). For example: if a build was executed on the local Agent as well as 9 remote Agents and the execution lasted for one hour, then we divide the 9 hours of execution on remote 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 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.合計時間に対するローカル Agent とリモート Agent で行われた処理の割合。 で割って、分散処理されたタスクの割合 (90%) を計算します。この値はリモート Agent コアで実行したビルドの合計時間を、すべての Agent (ローカルとリモート) で実行したビルドの合計時間で割って計算します。たとえば、ローカル Agent と 9 台のリモート Agent でビルドを 1 時間行った場合、リモート Agent コアで行った処理の合計時間 (9 時間) をビルドの合計時間 (10 時間) で割って、分散処理されたタスクの割合 (90%) を計算します。
Avg. Additional Cores NeededThis 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.ビルドで利用可能だった (実際には利用できなかった数) コアの平均数。ビルド処理中に、追加で必要とされるコア数が毎秒登録されます。1 秒ごとに追加で必要なコア数が集計され、その合計をビルドの処理時間 (秒) で割った値が表示されます。たとえば、値が「0」の場合は開発環境にコアを追加してもビルドの効率は向上しません。この値が大きいほど、コアを追加することによるパフォーマンスの向上を見込めます。
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 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 and dividing that by the number of cores on the local Agent. Since usage of the remote Agents is less efficient than usage of the initiator Agent (because of I/O and Network factors etc.), the result is divided in halfby 1.5. For example, if the initiator Agent has 4 cores and the build ran for an hour using an additional 12 cores on remote Agents. Then we take the 12 core-hours and divide that by the 4 cores on the initiator Agent which yields the result of 3 hours. We then take that number and divide it in halfby 1.5 to reach the result that the Time Saved was 1.52 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.  True – Every task that can be executed remotely is done remotely and not on the local Agent.  False – 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.

5 Top Distributed Builds Display

Image Removed
This pane shows the 5 individual build executions that achieved the highest Distributed Build percentage (for an explanation of this measure see Builds KPI Summary). Clicking on one of the builds displays a window with detailed information about that particular build. The data elements displayed in this window are the same as those displayed for the 5 Longest Builds (for an explanation of the elements see 5 Longest Builds Display).

Builds Grid

Image Removed

 
This pane displays detailed information about specific builds. A list of up to 10 builds is displayed at a time with a series of columns displaying detailed data about each build. You can scroll through the rest of the list by clicking the forward and backward arrows below the grid. You can customize the display by selecting which data columns are displayed. The builds can be sorted in ascending or descending order in relation to each of the columns. The data can be accessed in a manner that enables more in-depth analyses by entering Analysis Mode.

Builds Grid Filter

From the Build Grid Filter you can select which columns are displayed (for an explanation of the data displayed in each column see the Column Definition Table below). You can also enter Analysis Mode to enable more in-depth data analyses.

To select which columns are displayed:

5 Top Distributed Builds ディスプレイ

Image Added
このセクションでは、分散処理の割合が大きい上位 5 つのビルドを確認できます (分散処理の割合については前述の「ビルド KPI サマリー」を参照)。棒グラフ下の矢印アイコンをクリックするとビルドの詳細情報が表示されます。表示項目の詳細については「5 Longest Builds ディスプレイ」の項目リストをご覧ください。.

ビルド グリッド

Image Added

 
このセクションではビルドの詳細な情報を確認できます。リストに表示されるビルドは最大 10 個です。各ビルドの詳細が右側の列に表示されます。セクションの一番下に表示された矢印アイコンをクリックすると次のリストを表示できます。各項目をクリックして昇順 / 降順に並べ替えることができます。分析モード (Analysis Mode) ではより詳細な分析を行うことができます。

ビルド グリッド フィルター

フィルターを使って表示項目を絞り込むことができます (各項目の詳細は後述の「表示項目の詳細」を参照)。「分析モード」を開いてより詳細な分析を行うことができます。

表示項目の変更方法

1. セクション上部の [COLUMNS] フィルターをクリックします。
2. 表示項目がドロップダウン リストで表示されます。
3. 表示したい項目のチェックボックスをオンにします。
4. 選択済みの項目はチェックボックスをオフにすると非表示にできます (デフォルトではリストの上から 6 つの項目が選択済み)。
5. 選択した項目がグリッドに表示されます。

To enter Analysis Mode:

• Click Analysis Mode under the Builds Grid Filters choices.

Sorting

You can sort the builds listed in the grid in ascending or descending order for each of the columns.

To sort the builds listed in the grid:

分析モードの利用方法

• セクション上部の [Analysis Mode] をクリックします。

並び替え

グリッドに表示されているビルドは項目ごとに昇順 / 降順に並び替えることができます。

ビルドを並び替える

1. 各項目の上向き矢印をクリックすると、降順 (上→下) に並び替えることができます。
2. 各項目の下向き矢印をクリックすると、昇順 (下→上) に並び替えることができます。

Column Definition Table

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 Agent.

Distributed

The percentage of the build that was executed using remote Agents (i.e. Helpers) as opposed to the local Agent (i.e. Initiator). This value is calculated by taking the total duration of the build executed on remote Agents and dividing it by the total duration of builds executed on all Agents (including the local Agent). For example: if a build was executed on the local Agent as well as 9 remote Agents and the execution lasted for one hour, then we divide the 9 hours of execution on remote 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 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. 

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 . 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 and dividing that by the number of cores on the local Agent. Since usage of the remote Agents is less efficient than usage of the initiator Agent (because of I/O and Network factors etc.), the result is divided in halfby 1.5. For example, if the initiator Agent has 4 cores and the build ran for an hour using an additional 12 cores on remote Agents. Then we take the 12 core-hours and divide that by the 4 cores on the initiator Agent which yields the result of 3 hours. We then take that number and divide it by 1.5in half to reach the result that the Time Saved was 1.52 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 remotely and not on the local Agent. 
False – All Ttasks can be distributedexecuted both to on the local and remote Agents 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

表示項目の詳細

...