MAIA Build Report

Top boxes

The top boxes contain aggregated information for each build.

1. Build status: Shows if the Build process was successful or has failed.
2. Tests: Indicates Ok if all tests are reported ok. If any of the tests have errors/fails, the box will contain the number of errors and the total number of tests.
3. Delivery reports: The time since the latest delivery report was created.
4. License: The number of components that need a license approval.
5. CVE decisions: The number of detected CVEs that need a remediation decision.

Build Status

Build Status is the primary information in the report. Do we have a successful build or not, i.e. do we have software to release or not?

Build Success

1. Build status icon on top of the Build Report page shows a successful build status.
2. The report includes a link to the build activity page containing detailed information of the build process.
3. The activity page has a link to all Build log pages holding detailed log data for each component.

Build Failed

1. Build status icon on top of the Build Report page shows a failed build status.
2. A link to the build activity page containing detailed information of the failed build process.
3. Build activity information showing the error descriptions, here we have a problem to build the nginx-component
4. A link to the Build log pages.
5. Build log with detailed data, here regarding the failed nginx build process.

Build Comparison

What has changed since the previous build …, or since the previous delivery…, or what has changed between two selected builds?

Compare with a previous build.

1. Compare this build with a previous build on the identical environment. The comparison may also be made to a previously delivered build, or as an advanced comparison, to any build.
2. Table with all Issues that have a new Status vs the previous build.
3. Table with all code changes vs the previous build.
4. Table with all changes in components vs the previous build i.e. component rebuilt only, source code changed and rebuilt, component added and built or removed.

Commit information.

1. Links to all changes in code (commits).
2. New window with commit-info, i.e. what files are included and complete diff-information for each file.
3. Identity of deliveries where this commit was first time included (for each product)
4. Identity of builds where this commit was first time included (for each environment)
5. Identity of all tasks (Issues) referenced in this commit.

Issue information.

1. Links to all Issue with changed status (Open/Done).
2. New window with detailed Issue-info, i.e. all commits with ref to this Issue, status etc.

x

Test Results

Test results may continuously be posted to MAIA, that is analyzing and registering the results to the relevant Build Report.

Test result inspection.

1. The top icon shows the current status for all automated tests (here 2 tests have failed). The tests tab lists all test executions performed on this software.
2. The click-able progress bar shows the accumulated status for each execution.
3. When clicking the progressbar, a window that is listing all test suites is opened. Failed test suites are clearly indicated in red.
4. Open a test suite and all test groups and test cases are listed. Errors are shown in red. Each test case has a window with test case descriptions and verdicts.

External artifacts

About external software included by the build process and reported to MAIA.

External artifacts included in the software build.

1. The External artifacts tab lists all software components detected by the build process.
2. For each external component, the license type and text is specified.
3. Detected vulnerabilities are displayed. Detailed information are enabling analysis and management.
4. A list of deliveries where the software is included.
5. Current health status is retrieved from the external hosts.

License Management

A list of all components included in the build, and for each component a License presentation that can be managed and approved.

Vulnerabilities Management

An automated process to detect vulnerabilities in the components/versions used in the current software build.

Vulnerabilities detected in the software build.

1. The CVE tab lists all software components/versions that holds a detected vulnerability (CVE).
2. All CVEs are listed with the CVE-identity and its corresponding CVSS score.
3. Weakness (CWE) prioritization is displayed in a separate column.
4. Presenting exploit occurences.
5. A column displaying latest remediation decisions.