Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-12347

Migrate old definitions of leak period

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.0
    • Component/s: None
    • Labels:
      None
    • Edition:
      Community
    • Production Notes:
      None

      Description

      With MMF-1579, we will no longer support New Code Periods defined using a specific date or version. We will need to have a migration for those values.

      Project/branch settings

      If the new code period of a project is defined as a specific date or version, we migrate it by finding, in the main branch, the closest analysis to the date or an analysis that has the version change version. We do the same for long lived branches.

      If no suitable analysis is found, nothing will be set (use default value).

      The project setting will go back to default.

      Global settings

       We do what was described for "Project settings" for all projects that do not have a specific New Code Period set. The global New Code Period will be unset (default value).

       

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              duarte.meneses Duarte Meneses
              Reporter:
              duarte.meneses Duarte Meneses
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: