1.4.44. Migration to 7.4.0¶
1.4.44.1. Dashboard¶
Python wrapper of JSON API¶
Method count_issues in class bauhaus.dashboard.Project is now
deprecated in favor of method fetch_issues of the same class and might be removed in
a future version.
You should be able to easily replace all your uses of count_issues by
using fetch_issues and adding the two new keyword
arguments limit=0 and compute_total_row_count=True.
Drop of Classic UI¶
With 7.3 the Classic UI was deprecated and the Modern UI became default for new Dashboard configurations. Now the Classic UI has been removed and the Dashboard always uses the Modern UI.
1.4.44.2. Translation limits¶
Formerly, translation limits of your compiler were configured at different rules
(e.g. MisraC2012-1.1.limits). These limits should now be configured at the
compiler rule instead, using the graphical configuration interface.
The old options continue to work in 7.4.0 but are deprecated and scheduled for
removal in future releases.
Also, rules MisraC2012-5.1/2/4/5, MisraC-5.1 and CertC-DCL23
now refer to the appropriate translation limit by default, and fall back to their
rule-specific maxlen parameter only if an explicit value is set there manually.
These changes may cause differences in reported issues when updating, and you should configure appropriate translation limits at your compiler rule before finishing the migration.
1.4.44.3. Architecture-RhapsodyImporter¶
The types of the options ignore_rhapsody_methods and
enable_rhapsody_methods have been changed from
list to set. This does not introduce breaking changes
in the JSON configuration format. However, this is a breaking change if
you configure these two options via Python configuration files. Now, the
Python set API has to be used instead of the list API.
1.4.44.4. Legacy Continuous Integration Mailer¶
We now provide an alternative to the legacy mailer-tool of cibuild that
also works in combination with axivion_ci.
It is basically an example python script that can be tuned for some specific use cases and might be more suited to your workflow than the dashboard integrated Erosion Notification System. It is shipped as example/reports/report_delta_mailer.py and needs to be executed via report_runner after axivion_ci inside your CI pipeline.
1.4.44.5. Stylecheck¶
Since AutosarC++-A16.2.3 demands explicit include directives to be added for all symbols used in a file, being compliant with AutosarC++-A16.2.3 often causes violations of the covered_include message of AutosarC++-A16.2.2. In consequence, AutosarC++-A16.2.2 now disables the covered_include message to avoid collisions.