Closed philipooo closed 2 years ago
The plugin uses /d:sonar.branch when it detects a version below 7. If that's does not meet your needs, can you elaborate on which edition/version you use? Do you know the documentation of that version? Do you know a docker image of that version i can test against?
The problem is that we use version 7.3, but not the developer edition which comes with support for sonar.branch. So we still need to use the old sonar.branch.name parameter (called legacy branching in SonarQube) with the community edition.
We have a similar issue with 6.7.5 Data Center / Enterprise edition. Because the version is below 7, the plugin switches to /d:sonar.branch. But /d:sonar.branch creates a new project whereas /d:sonar.branch.name creates a new branch within an existing project which is what we expect.
The documentation for this version is sparse but this is what I could find: https://docs.sonarqube.org/display/SONARQUBE67/Documentation
I do not have a docker image, but the following page has a link to download the editions (not sure about the licensing though): https://docs.sonarqube.org/display/SONARQUBE67/SonarSource+Editions
So like @philipooo mentioned, it would be helpful to have an additional flag/parameter which will allow us to choose between sonar.branch and sonar.branch.name irrespective of the Sonar version.
I think this has been implemented? It works fine for me.
Is this still an issue @philipooo? If so we can reopen the ticket.
It would be nice if there was a flag to use legacy branching. We want to use the "Branching-Feature" of SonarQube, but can
t use sonar.branch.name because we don
t have the developer edition. So we need to use sonar.branch to set the branch-name.