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

Fix Monorepo Bitbucket Report Key generation for long SQ Project Keys

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.9.2, 9.1
    • Component/s: Branch & PR
    • Labels:
      None
    • Edition:
      Enterprise
    • Production Notes:
      None

      Description

      When decorating a Bitbucket monorepo PR, SonarQube creates a report object in bitbucket,  with a suffix and the SQ Project Key.

      Since a SQ Project key can have 400 characters, the resulting report key may be too long for Bitbucket

      • Bitbucket Server limits this key to 50 characters.
      • Bitbucket Cloud limits this key to 40 characters

      Therefore, PR decoration will fail.

      With SONAR-15054 we are showing users a warning to explain to them why Pull Request decoration will fail in this cases.

      However, we should fix this problem and let users have their Monorepo PRs decorated in Bitbucket.

      We should decouple the Report Key generation from the SQ Project Key, to make sure it will meet the Bitbucket length limits.

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mathieu.suen Mathieu Suen
              Reporter:
              belen.pruvost Belén Pruvost
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: