Closed santus444 closed 5 years ago
Related to #20
The README file contains some hints about the importance of setting up the base URL of the SonarQube instance. Thanks for the input @santus444 . I won't be merging this PR as I feel that the existing documentation should be enough now. Thanks for your input, though! Really appreciated your feedback.
I added the comment as I faced below issue. I was using a sandbox instance of sonarqube which had different host name than production version. But as the sandbox was cloned from production, the Server base URL remained same. When the analysis was performed, the sonar runner printed following in the logs Actual: ce_task_url http://prod-sonarqube.com:9009/api/ce/task?id=AWG6njze0E05u_gH2XqY dashboard_url http://prod-sonarqube.com:9009/dashboard/index/lib_app project_key lib_app scanner_type cli server_url http://prod-sonarqube.com:9009 server_version 6.7.0.33306
Expected: ce_task_url http://sandbox-sonarqube.com:9009/api/ce/task?id=AWG6njze0E05u_gH2XqY dashboard_url http://sandbox-sonarqube.com:9009/dashboard/index/lib_app project_key lib_app scanner_type cli server_url http://sandbox-sonarqube.com:9009 server_version 6.7.0.33306
This was due to the Server base URL configuration. This could very well be sonarqube scanner cli issue but the logs in concourse were misleading, pointing to wrong instance. It may not be even configured with correct host name as it is only used to create email links.
This issue also helped me in resolving the issue I was having due to slash: https://github.com/cathive/concourse-sonarqube-resource/issues/10