You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you added SQL Server Reporting Services at installation, then your on-premises Team Foundation Server (TFS) deployment is configured with a data warehouse, SQL Server Analysis Services cube, and Reporting Services Reports. If you didn't add these services previously and want to add them now, see [Add a report server to your deployment](../admin/add-a-report-server.md?toc=/azure/devops/report/toc.json&bc=/azure/devops/report/breadcrumb/toc.json).
18
+
If you added SQL Server Reporting Services at installation, then your on-premises Azure DevOps deployment is configured with:
19
+
- A data warehouse
20
+
- SQL Server Analysis Services cube
21
+
- Reporting Services Reports
22
+
23
+
If you didn't add these services previously and want to add them now, see [Add a report server to your deployment](../admin/add-a-report-server.md?toc=/azure/devops/report/toc.json&bc=/azure/devops/report/breadcrumb/toc.json).
19
24
20
-
You can create or customize your own Reporting Services reports which support the following scenarios:
25
+
You can create or customize your own Reporting Services reports that support the following scenarios:
21
26
22
27
- Allow users to update the report without granting them read access to the databases.
23
28
- Share your reports in Team Explorer under the Reports folder.
@@ -26,10 +31,16 @@ You can create or customize your own Reporting Services reports which support th
26
31
- Use Transact-SQL queries to retrieve the data for your reports.
27
32
28
33
29
-
To learn more, see the following topics:
34
+
To learn more, see the following articles:
30
35
-[Creating Reports for Team Foundation Server 2010](../../boards/work-items/guidance/agile-process.md?viewFallbackFrom=vsts) describes how to create reports that you can view by using Report Manager. (There are only minor schema changes introduced for the TFS 2015 relational warehouse since TFS 2010).
31
36
-[Customizing Reports for Team Foundation Server 2010](/previous-versions/visualstudio/visual-studio-2012/dd380700(v=vs.110)) describes how to customize the default reports for Reporting Services that are provided with each process template. These reports use queries that are written in either SQL or Multidimensional Expressions (MDX). (There are only minor schema changes introduced for the TFS 2015 cube since TFS 2010).
32
-
-[Table reference for the relational warehouse database](table-reference-relational-warehouse-database.md). The warehouse contains data about builds, source code, test results and code coverage, and work items such as tasks and bugs. Data in the warehouse is collected from the operational stores and organized in a set of tables, views, and table-valued functions from which you can design reports. You can explore relationships between the integrated data sets by directly querying and creating reports from data that is stored in the relational warehouse database.
37
+
-[Table reference for the relational warehouse database](table-reference-relational-warehouse-database.md). The warehouse contains data about
38
+
- Builds
39
+
- Source code
40
+
- Test results and code coverage
41
+
- Work items such as tasks and bugs.
42
+
43
+
Data in the warehouse is collected from the operational stores and organized in a set of tables, views, and table-valued functions from which you can design reports. You can explore relationships between the integrated data sets by directly querying and creating reports from data that is stored in the relational warehouse database.
33
44
34
45
![Team Foundation Warehouse](media/teamproj_warehouse.png"TeamProj_Warehouse")
35
46
@@ -43,12 +54,12 @@ To learn more, see the following topics:
43
54
44
55
You can access both the relational data warehouse and the Analysis Services cube to create highly customized reports by using these authoring tools.
45
56
46
-
-**Report Builder** is an intuitive environment for authoring reports. This application is optimized for Microsoft Office so that business users can work in that familiar environment. You can use Report Builder to work with data, define a layout, preview a report, and publish a report to a report server or a SharePoint site. This application includes a wizard for creating tables or charts, in addition to query builders and an expression editor. It also supports the advanced reporting features in SQL Server Reporting Services.
57
+
-**Report Builder** is an intuitive environment for authoring reports. This application is optimized for Microsoft Office so that business users can work in that familiar environment. You can use Report Builder to work with data, define a layout, preview a report, and publish a report to a report server or a SharePoint site. This application includes a wizard for creating tables or charts, query builders, and an expression editor. It also supports the advanced reporting features in SQL Server Reporting Services.
47
58
48
59
You can download Report Builder for free from the following pages on the Microsoft web site:
-**[Report Builder 2.0 (for SQL Server 2008](https://www.microsoft.com/download/details.aspx?id=24085)**
51
-
-**Report Designer** is a graphical interface for creating full-featured Reporting Services reports. After your report is finished, you have access to the full functionality for managing Reporting Services reports. To use Report Designer, you must know how to connect to and query a data source, but you do not have to know Report Definition Language (RDL).
62
+
-**Report Designer** is a graphical interface for creating full-featured Reporting Services reports. After your report is finished, you have access to the full functionality for managing Reporting Services reports. To use Report Designer, you must know how to connect to and query a data source. You don't have to know Report Definition Language (RDL).
52
63
53
64
To use Report Designer, you must have Visual Studio and SQL Server Business Intelligence Development Studio.
By using the Build perspective, you can view just the measures, dimensions, and attributes in the SQL Server Analysis Services cube for Visual Studio Team Foundation Server that pertain to the build process. For example, you can use these measures to determine how many builds are failing and how much of the code changed within a build.
18
+
By using the Build perspective, you can view just the measures, dimensions, and attributes in the SQL Server Analysis Services cube for Azure DevOps Server that pertain to the build process. For example, you can use these measures to determine how many builds are failing and how much of the code changed within a build.
19
19
20
20
> [!IMPORTANT]
21
21
> The Build Measures and perspectives are only applicable for XAML builds, which are deprecated for TFS 2018 and later versions. If your build process isn't based on XAML builds, the measures, perspectives,reports, and the TFS Warehouse for builds won't yield any meaningful data.
@@ -49,11 +49,11 @@ By using PivotChart reports in Excel, you can display the build status over time
49
49
50
50
The [Agile](../../boards/work-items/guidance/agile-process.md) and [CMMI](../../boards/work-items/guidance/cmmi-process.md) process templates include the Build Status report in Excel. For more information, see [Build Status](/previous-versions/azure/devops/report/excel/build-status-excel-report).
51
51
52
-
###Pivot field selection and filters
52
+
## Pivot field selection and filters
53
53
54
54
![Pivot Fields for Build Summary Status report](media/alm_rpt_pivot_build.png"ALM_RPT_Pivot_Build")
55
55
56
-
You can create the summary report for build status by performing the following steps:
56
+
You can create the summary report for build status by carrying out the following steps:
57
57
58
58
1. In Excel, connect to the Analysis Services cube for Azure DevOps Server, and insert a PivotChart report.
59
59
@@ -79,28 +79,32 @@ By using PivotChart reports in Excel, you can display the build status over time
79
79
80
80
81
81
<aname="measures"></a>
82
-
## Build measures
82
+
83
+
## Build measures
84
+
83
85
The following table describes the measures that are associated with builds. The **Build Coverage** measure group requires that the test team instrument tests to gather code coverage data. For more information, see [Required activities](#tracking) later in this article. For an example of a report that uses several of these measures, see [Build Quality Indicators](build-quality-indicators-report.md).
|Build Details|Build Details Count|Number of times that a specific build has been run.|
88
90
||Build Duration|Number of minutes that the build took to finish.|
89
91
|Build Changeset|Build Changeset Count|Number of changesets in the selected set of builds.|
90
-
|Build Coverage|Blocks Covered|Number of blocks that the selected build covers. If multiple test runs are performed against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover blocks that overlap.|
91
-
||Blocks Not Covered|Number of blocks that the selected build does not cover. If multiple test runs are performed against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover blocks that overlap.|
92
+
|Build Coverage|Blocks Covered|Number of blocks that the selected build covers. If multiple test runs are carried out against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover blocks that overlap.|
93
+
||Blocks Not Covered|Number of blocks that the selected build doesn't cover. If multiple test runs are carried out against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover blocks that overlap.|
92
94
||Build Coverage|Number of builds that are associated with code coverage statistics.|
93
-
||Lines Covered|Number of lines that the selected build covers. If multiple test runs are performed against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover lines that overlap.|
94
-
||Lines Not Covered|Number of lines that the selected build does not cover. If multiple test runs are performed against a build, the build coverage reflects the combined coverage of the runs. However, the runs might cover lines that overlap.|
95
-
||Lines Partially Covered|Number of lines that the selected build partially covers. If multiple test runs are performed against a build, the build coverage reflects the combined coverage of the runs. However, the runs might cover lines that overlap.|
95
+
||Lines Covered|Number of lines that the selected build covers. If multiple test runs are carried out against a build, the build coverage reflects the combined coverage of the runs. However, the runs may cover lines that overlap.|
96
+
||Lines Not Covered|Number of lines that the selected build doesn't cover. If multiple test runs are carried out against a build, the build coverage reflects the combined coverage of the runs. However, the runs might cover lines that overlap.|
97
+
||Lines Partially Covered|Number of lines that the selected build partially covers. If multiple test runs are carried out against a build, the build coverage reflects the combined coverage of the runs. However, the runs might cover lines that overlap.|
96
98
|Build Project|Build Project Count|Number of .csproj files, .vbproj files, and other project files in the selected set of builds.|
97
99
||Compile Errors|Number of compile errors that occurred for the selected builds.|
98
100
||Compile Warnings|Number of compile warnings that occurred for the selected builds.|
99
101
||Static Analysis Errors|Number of static analysis errors that occurred for the selected builds.|
100
102
||Static Analysis Warnings|Number of static analysis warnings that occurred for the selected builds.|
101
103
102
104
<aname="dimensions"></a>
103
-
## Dimensions and attributes in the Build perspective that support filtering and categorization
105
+
106
+
## Dimensions and attributes in the Build perspective
107
+
104
108
You can use the attributes in the following table to aggregate a measure, filter a report, or specify a report axis. These attributes supplement the **Team Project** and **Date** shared dimensions that [Working with Shared Dimensions](shared-dimensions-in-the-analysis-services-cube.md) describes.
105
109
106
110
> [!NOTE]
@@ -113,8 +117,8 @@ By using PivotChart reports in Excel, you can display the build status over time
113
117
||Build ID|The number that is assigned to the build. Each time that a particular build pipeline is run, the **Build ID** is incremented by 1.|
114
118
||Build Name|The name or expression that uniquely identifies a build. For more information, see [build pipeline options](../../pipelines/build/options.md).|
115
119
||Build Start Time|The date and time when the build started.|
116
-
||Build Type|The reason why the build was run. Build types are associated with the trigger that was defined for the build. Team Foundation Server supports the following types of builds: manual, continuous (triggered by every check-in), rolling (accumulate check-ins until the previous build finishes), gated check-in, and scheduled. For more information, see [Build pipeline triggers](../../pipelines/build/triggers.md).|
117
-
||Drop Location|The Uniform Resource Locator (URL) for the completed build. A URL specifies the protocol with which web browsers will to locate Internet resources. Each URL includes the name of the server on which the details of the build resides. You can also include the path to a resource.|
120
+
||Build Type|The reason why the build was run. Build types are associated with the trigger that was defined for the build. Azure DevOps Server supports the following types of builds: manual, continuous (triggered by every check-in), rolling (accumulate check-ins until the previous build finishes), gated check-in, and scheduled. For more information, see [Build pipeline triggers](../../pipelines/build/triggers.md).|
121
+
||Drop Location|The Uniform Resource Locator (URL) for the completed build. A URL specifies the protocol with which web browsers will locate Internet resources. Each URL includes the name of the server on which the details of the build resides. You can also include the path to a resource.|
118
122
|Build Flavor|Build Flavor|(Published test results only) A name that designates the category of builds that was assigned to a set of completed builds that were published as part of a test run. For example, a build flavor can designate a beta release or final release. For more information, see [Command-Line options for publishing test results](/previous-versions/ms243151(v=vs.140)).|
119
123
|Build Platform|Build Platform|The name of the platform for which an end-to-end (not desktop) build was made (for example, **x86** or **Any CPU**). For an example of a report that uses this attribute, see [Build Summary](build-summary-report.md). For more information, see [How do I build multiple configurations for multiple platforms?](../../pipelines/tasks/build/visual-studio-build.md#how-do-i-build-multiple-configurations-for-multiple-platforms).|
120
124
|Build Quality|Build Quality|The quality of the build. For example, you can rate a completed build's quality as **Ready for Deployment**, **Rejected**, or **Under Investigation**. |
@@ -124,15 +128,17 @@ By using PivotChart reports in Excel, you can display the build status over time
124
128
|Version Control Changeset|Changeset ID|The number that is assigned to the changeset.|
125
129
||Checked In By|The user name of the team member who checked in the changeset.|
126
130
||Description|The check-in comment that is associated with the changeset.|
127
-
||Policy Override Comment|The comment that is provided when a policy is overridden. If a policy was not overridden with a changeset, the field is null.|
131
+
||Policy Override Comment|The comment that is provided when a policy is overridden. If a policy wasn't overridden with a changeset, the field is null.|
128
132
129
133
## <aname="tracking"></a> Required activities
130
-
To create reports that contain useful data about builds, team members should review the information in the following topics:
134
+
135
+
To create reports that contain useful data about builds, team members should review the information in the following articles:
131
136
132
137
-[Run tests in your build process](../../pipelines/index.yml)
133
138
-[Using Code Coverage to Determine How Much Code is being Tested](/visualstudio/test/using-code-coverage-to-determine-how-much-code-is-being-tested)
0 commit comments