6.2.9. ImportAnalysisResults

Import analysis results from previous axivion_analysis run

This rule imports all violations from a previous analysis run into the current analysis run.

The file containing the violations to be imported can be created by activating the /Results/Reports/AnalysisResultsReports rule in the configuration of previous analysis, or by using axivion_analysis --output_binary.

This can be used to combine the analysis results for multiple IRs into a single project.

Note that this is a simple import of violations. As such, it always computes the union of violations; even in cases (e.g. dead code) where the intersection might be more appropriate.

Possible Messages

This rule has no predefined messages.

6.2.9.1. Options

• This rule shares the following common options: excludes, includes

• The following places define options that affect this rule: Analysis-GlobalOptions

basepath

basepath : bauhaus.analysis.config.LayerRelativePath | None = None

This option should be set to a directory in the workspace of the current analysis run that corresponds to the project directory of the previous analysis run. When this option is None, violations will be imported as-is: any violations that were previously reported relative to the project directory of the previous analysis, will be treated as relative to the project directory of the current analysis. When this option is set, violations with relative paths will instead be interpreted as being relative to the value of this option.

 

filename

filename : bauhaus.analysis.config.LayerRelativePath = 'None (value must be set)'

Path to the file containing the analysis results. This must have been previously created using the axivion_analysis --output_binary option or the BinaryReport rule.