You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am providing PR #1953 that has our build script check for that secret and pass it to SonarQube. The PR will silence SonarQube until a SONAR_HOST_URL secret is provided.
According to the above documentation, we should have 1) a SonarQube Server, and 2) a Github App to receive the info from the server. We might well have those things from when this was working. But I can't see them since I am not an owner of the project. If we don't have them, we will need to create them following the instructions in the above documentation.
@MarcinOrlowski might be able to tell us where they are and what URL to use if @BFH-ktt1 doesn't see them. Any other insight @MarcinOrlowski has about getting this to work would be much appreciated.
The text was updated successfully, but these errors were encountered:
SonarQube is causing our build script to die on merge to main. Specifically, it is giving an error that it can't find a server at http://localhost:9000. According to the documentation at https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/, we should be giving it the URL of the SonarQube Server in SONAR_HOST_URL and we should have a secret of that name with the URL as its value.
I am providing PR #1953 that has our build script check for that secret and pass it to SonarQube. The PR will silence SonarQube until a SONAR_HOST_URL secret is provided.
According to the above documentation, we should have 1) a SonarQube Server, and 2) a Github App to receive the info from the server. We might well have those things from when this was working. But I can't see them since I am not an owner of the project. If we don't have them, we will need to create them following the instructions in the above documentation.
@MarcinOrlowski might be able to tell us where they are and what URL to use if @BFH-ktt1 doesn't see them. Any other insight @MarcinOrlowski has about getting this to work would be much appreciated.
The text was updated successfully, but these errors were encountered: