SonarQube Plugins
  1. SonarQube Plugins
  2. SONARPLUGINS-1876

Make the "sonar.scm.url" parameter optional when using Git and Subversion

    Details

    • Number of attachments :
      0

      Issue Links

        Activity

        Hide
        David Gageot added a comment -

        This parameter is now optional for git,hg and svn

        Show
        David Gageot added a comment - This parameter is now optional for git,hg and svn
        Hide
        Freddy Mallet added a comment -

        I always get the following exception :

        on project example-ut-maven-jacoco-runTests: Can not execute Sonar: SCM URL must not be blank. Please check the parameter "sonar.scm.url" or the <scm> section of Maven pom
        
        Show
        Freddy Mallet added a comment - I always get the following exception : on project example-ut-maven-jacoco-runTests: Can not execute Sonar: SCM URL must not be blank. Please check the parameter "sonar.scm.url" or the <scm> section of Maven pom
        Hide
        David Gageot added a comment -

        It's fixed now. I tested with projects and sub-modules, with maven and java runner.
        I also added logs to tell the user what's going on during the phase where sonar is trying to guess which scm provider is used.

        Show
        David Gageot added a comment - It's fixed now. I tested with projects and sub-modules, with maven and java runner. I also added logs to tell the user what's going on during the phase where sonar is trying to guess which scm provider is used.
        Hide
        Freddy Mallet added a comment -

        Works well David ! Tested with both Subversion and Git.

        I really do think that with Subversion, Git and Mercurial we should no more take into account the sonar.scm.url parameter to prevent failing when this parameter is badly defined in the maven pom.xml file. I'm reopening this ticket just to be sure to have this discussion

        Show
        Freddy Mallet added a comment - Works well David ! Tested with both Subversion and Git. I really do think that with Subversion, Git and Mercurial we should no more take into account the sonar.scm.url parameter to prevent failing when this parameter is badly defined in the maven pom.xml file. I'm reopening this ticket just to be sure to have this discussion
        Hide
        David Gageot added a comment -

        Done. Now guessing happens before reading the url settings or the maven scm url

        Show
        David Gageot added a comment - Done. Now guessing happens before reading the url settings or the maven scm url
        Hide
        Freddy Mallet added a comment -

        Manually tested !

        Show
        Freddy Mallet added a comment - Manually tested !
        Hide
        David Gageot added a comment -

        ITs added

        Show
        David Gageot added a comment - ITs added

          People

          • Assignee:
            David Gageot
            Reporter:
            Freddy Mallet
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: