Sonar Plugins

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

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: SCM-ACTIVITY-1.5
  • Component/s: SCM Activity
  • Labels:
    None
  • Number of attachments :
    0

Issue Links

is related to

New Feature - A new feature of the product, which has yet to be developed. SONARPLUGINS-1450 Add the ability to support multiple credential for multiple servers at global level

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Task - A task that needs to be done. SONARPLUGINS-1092 Use API from Maven SCM to validate URL instead of own implementation

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
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
Permalink
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
Permalink
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
Permalink
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
Permalink
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
Permalink
Freddy Mallet added a comment -

Manually tested !

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

ITs added

Show
David Gageot added a comment - ITs added

People

  • Assignee:
    David Gageot
    Reporter:
    Freddy Mallet
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: