Skip to content

Best Practices for Build Audit Reports

What are Build Audits?

The governing processes for Build Audits is found in the Quality Management System (QMS): http://gqms.medtronic.com/ DOC000689 Rev U – Design Controls: Top Level Procedure DOC000663 Rev V – Design Controls: Design Verification

The Build Audit Report is mentioned in the two procedures above. It does not define the content to be contained in a build audit or a specific form to be used. It is used as an input to the Design Verification. The Build Audit Report may be different depending on the structure and complexity of the deliverable product. It typically contains a "Difference Report", "Inventory Report" and for complex systems a "Master Memo"

Difference Report

The Difference Report shows the code changes that comprise the released product, their parent Tasks and the Task's parent User Story work items from the work item management system currently Team Foundation Server (TFS). There may be multiple difference reports for a release depending on the number of branches that code was developed on. Because the Difference Report show difference between any two labels on a TFVC source branch, it can be used to identify "orphaned" changesets that do not have related Tasks or the related Tasks do not have parent User Stories. There is also an option to report the state of each related Task and its parent User Story.

The difference report is generated from a website created and managed by Kevin Ehrler. The website is hosted on an on-premise server in the ENT domain: amw00885.ent.core.medtronic.com Difference Report Website

  • Current TFS Use The difference report is used currently used by many projects in TFS either as part of a build audit report, a method of finding "orphaned" changesets\Tasks or a view of overall status. CareLink Releases and MAS Releases currently use the Difference Report as part of their build audits.

  • Future AZDO Use Kevin Ehrler is updating the Difference Report to handle GIT repositories in AZDO for near future.

Code Inventory Report

The Code Inventory Report lists all the files comprising the release. For each file it lists the product, changeset, data\time of the change and full file path in the repository. The Code Inventory Report is generated from by a website created and managed by Kevin Ehrler. The website is hosted on an on-premise server in the ENT domain: amw00885.ent.core.medtronic.com Inventory Report Website

  • Current TFS Use The inventory report is currently used by CareLink Releases and MAS Releases as part of their build audits.

  • Future AZDO Use Kevin Ehrler is updating the Inventory Report to handle GIT repositories in AZDO for near future.

Master Memo

The Master Memo is used for systems that contain multiple builds and sub-systems. For a release, it lists the following: - Release Name - Sub-system names and versions - Submittable files for the release and comparison to known production versions - Octopus Packages for each Sub-system. - Non-submittable NuGet Packages

The Master Memo is generated from by a website created and managed by Kevin Ehrler. The Master Memo website utilizes information from the Octopus Deployment system, a Configuration Management Database (CMDB) and Team Foundation System (TFS) to generate Master Memo. The website is hosted on an on-premise server in the ENT domain: amw00885.ent.core.medtronic.com Master Memo Website

  • Current TFS Use The Master Memo is currently used by CareLink Releases and MAS Releases as part of their build audits.

  • Future AZDO Use Kevin Ehrler is updating the Master Memo to handle GIT repositories in AZDO for near future.

AZDO Future Questions

- These reports are currently executed from an on-premise Windows Server.  Will this be moved to a cloud server?
- Will reporting on Pull Requests be needed additionally or replace one or more of these build audit reports?