MAIA Build Report
MAIA is creating a comprehensive report for each software build. The report offers both summarized high-level information and a lot of low-level details for all stakeholders.
MAIA Build Report
Top boxes
The top boxes contain aggregated information for each build.
- Build status: Shows if the Build process was successful or has failed.
- 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.
- Delivery reports: The time since the latest delivery report was created.
- License: The number of components that need a license approval.
- CVE decisions: The number of detected CVEs that need a remediation decision.
Top boxes
The top boxes contain aggregated information for each build.
- Build status: Shows if the Build process was successful or has failed.
- 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.
- Delivery reports: The time since the latest delivery report was created.
- License: The number of components that need a license approval.
- CVE decisions: The number of detected CVEs that need a remediation decision.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
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?[/bsf-info-box][bsf-info-box icon_size=”32″]
Build Success
- Build status icon on top of the Build Report page shows a successful build status.
- The report includes a link to the build activity page containing detailed information of the build process.
- The activity page has a link to all Build log pages holding detailed log data for each component.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
Build Failed
- Build status icon on top of the Build Report page shows a failed build status.
- A link to the build activity page containing detailed information of the failed build process.
- Build activity information showing the error descriptions, here we have a problem to build the nginx-component
- A link to the Build log pages.
- Build log with detailed data, here regarding the failed nginx build process.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
Build Comparison
What has changed since the previous build …, or since the previous delivery…, or what has changed between two selected builds?[/bsf-info-box][bsf-info-box icon_size=”32″]
Compare with a previous build.
- 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.
- Table with all Issues that have a new Status vs the previous build.
- Table with all code changes vs the previous build.
- 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.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
Commit information.
- Links to all changes in code (commits).
- New window with commit-info, i.e. what files are included and complete diff-information for each file.
- Identity of deliveries where this commit was first time included (for each product)
- Identity of builds where this commit was first time included (for each environment)
- Identity of all tasks (Issues) referenced in this commit.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
Test Results
Test results may continuously be posted to MAIA, that is analyzing and registering the results to the relevant Build Report.[/bsf-info-box][bsf-info-box icon_size=”32″]
Test result inspection.
- 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.
- The click-able progress bar shows the accumulated status for each execution.
- When clicking the progressbar, a window that is listing all test suites is opened. Failed test suites are clearly indicated in red.
- 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.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
External artifacts
About external software included by the build process and reported to MAIA.[/bsf-info-box][bsf-info-box icon_size=”32″]
External artifacts included in the software build.
- The External artifacts tab lists all software components detected by the build process.
- For each external component, the license type and text is specified.
- Detected vulnerabilities are displayed. Detailed information are enabling analysis and management.
- A list of deliveries where the software is included.
- Current health status is retrieved from the external hosts.
[/bsf-info-box]
[bsf-info-box icon_size=”32″]
Vulnerabilities Management
An automated process to detect vulnerabilities in the components/versions used in the current software build.[/bsf-info-box][bsf-info-box icon_size=”32″]
Vulnerabilities detected in the software build.
- The CVE tab lists all software components/versions that holds a detected vulnerability (CVE).
- All CVEs are listed with the CVE-identity and its corresponding CVSS score.
- Weakness (CWE) prioritization is displayed in a separate column.
- Presenting exploit occurences.
- A column displaying latest remediation decisions.
[/bsf-info-box]
[info_list][/info_list]