Example build report.

build report

This is an example of a build report created by MAIA Software. It is a top-level (a suite) build report where information about all sub-level-builds are included. Sub-level-builds also have identically structured reports.

The report contains a number of topics:

  • heading – build identity and version, time, status, etc.
  • includes – blocks included in the build.
  • dependencies – dependencies (and versions) for this block.
  • changes – changes in source code, added/removed components, etc.
  • diff tool – tool to compare this build with other versions.
  • vulnerabilities – vulnerabilities in this build.
  • build info – info.
  • test results – test results for this build, unit/integration/system test etc.

heading

Build Report

 

click img to enlarge

This is the heading part of a build report, with:

  • build identity (name) and a unique version number.
  • build status (Success..Fail…etc)
  • block identity (
  • track identity (branch)
  • build label
  • build host name (and url)
  • build session id, url to detailed info about the build process (logs).
  • test results, url to detailed info about test results for this build.

includes

Build Report

click img to enlarge

The first TAB is the includes part of a build report, with the sections:

  • Delivery Reports, name, date and url:s to all delivery reports created from this build.
  • Artifacts created, names and url:s to all artifacts…ISOs, signature files etc.
  • A list, and url:s, of all included (sub-level) blocks and versions (their builds) in the (top-level) build.
  • A list, and url:s, of source code (all levels) included in the build.

dependencies

Build Report

click img to enlarge

The second TAB is the dependencies part of a build report, with:

  • A list , and url:s, of all dependencies for this (and sub-level) builds.

changes

Build Report

click img to enlarge

The third TAB is the changes part of a build report. It lists all changes recorded from the previous build. This part contains the sections:

  • Done Issues. A list of issues that have changed to status Done.
  • Resolved Issues. A list of issues that have changed to status Resolved.
  • Open Issues. A list of new issues opened after the previous build

All issues have an url to more detailed info. An issue (work item/task) registered in MAIA may be synchronized with an origin in a tracking system.

  • A table (with sub-tables) with all code changes since the previous build (and url:s to more info).

diff tool

Build Report

click img to enlarge

The fourth TAB is the diff tool part of a build report. Here you can select any other build to compare and present changes. Very useful when to view changes from last delivery, or last week, from sprint start, etc.

The DIFF result has the same structure as in the previous TAB (changes).

Build Report

click img to enlarge

vulnerabilities

Build Report
Build Report

click img to enlarge

The fifth TAB is the vulnerabilities part of a build report.

This page shows a table of included blocks (components) and all their detected vulnerabilities, respective. Vulnerabilities are classified and there are url:s to each vulnerability report for more information and evaluation.

There is a toggle-button between Table- and Tree-view of the vulnerabilities status.

 

build info

Build Report

click img to enlarge

The sixth TAB is the build info part of a build report.

A list of extra information about the build:

  • Previous build: name, version and url to.
  • Previous build: build time.
  • Version of this block.
  • Identity of last commit (before build).
  • Code revision (version).
  • Number of artifacts created.

test results

Build Report

click img to enlarge

In the build report header section there is an url to the related test report, with detailed information about all test results.

Build Report

click img to enlarge

This website uses cookies to give you the best experience. By continuing you agree to our cookie policy.