-
Notifications
You must be signed in to change notification settings - Fork 53
Why cant specify projectKey and projectName? #24
Comments
As a solution, I can get it working using following setup: drone.yml:
sonar-project.properties (in branch-1):
sonar-project.properties (in branch-2):
Anyway, I think it would be great that we can be able to set projectKey and projectName as settings in drone pipeline, something like this:
This way, the configuration is made in the specific step for each branch, and sonar-project.properties is not needed. |
Hi can you please help I am also facing the same issue. Not able to specify projectKey and Name parameters. I tried adding it to sonar-project.properties but it is not picking up the values. I am using drone v 0.8 , so usingProperties flag does not work for me. |
Hi @Hpareek07 I cant help you. As you can see in my example, I am using It seems that this feature has no interest in the community. If I have some spare time I will try to fork the plugin to do it myself, but cant promise anything |
linked to #28 |
According to docs:
why not be able to set projectKey and projectName using settings in drone pipeline?
I have a project with a lot of git branches, and I want to send to sonarqube each branch as a different project. With the actual approach, I need to set different settings in sonar-project.properties for each branch to get that.
It would be great if I can set key and project name in the plugin settings, as I have different steps in drone.yml for each branch.
I dont know if there is any technical reason for this
The text was updated successfully, but these errors were encountered: