Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-124665

Use Axivion to catch API relevant issues during CI checks

    XMLWordPrintable

Details

    • User Story
    • Resolution: Unresolved
    • P2: Important
    • None
    • None
    • Core: Other
    • None
    • PM Pending Features

    Description

      Our API review has become a rather large effort and partly leads to release delays. On reason is that API commits don't always follow Qt API & BC rules. The wiki below lists several such rules which developers should be aware of:

       

      https://wiki.qt.io/Things_To_Look_Out_For_In_Reviews

       

      We should consider adding those rules to Axivion as part of an Qt API rule set and add run those rules during a CI integration as blocking rule. This requires implementation of above rules on the Axivion tooling side.

      Attachments

        Issue Links

          resulted from

          User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QTBUG-122619 Review Axivion Scan results for QtCore and fix if needed

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QTBUG-125026 Review Axivion Scan results for QtNetwork and fix if needed

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ablasche Alex Blasche
              ablasche Alex Blasche
              Vladimir Minenko Vladimir Minenko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes