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
The login parameter is required on the resource definition. However my Sonar instance is on a private network and doesn't require a username or access token to push analysis results to.
Leaving the login field blank in my pipeline YAML doesn't seem to work.
How can I use this resource with an open Sonarqube instance?
The text was updated successfully, but these errors were encountered:
You are right, the login parameter is mandatory.
I assume that even when running SonarQube on a private network it is a good idea to create a different user for the CI/CD system. One advantage e.g. is that you can easily distinguish between analysis-runs that have been triggered by the CI/CD system and those triggered by another user.
assets/common.sh would need to be patched if an open SonarQube instance is indeed a valid use-case. I will probably not find the time to provide a patch myself in the next few days-- but I'll gladly except one if it doesn't break anyhing else. ;-)
The
login
parameter is required on the resource definition. However my Sonar instance is on a private network and doesn't require a username or access token to push analysis results to.Leaving the login field blank in my pipeline YAML doesn't seem to work.
How can I use this resource with an open Sonarqube instance?
The text was updated successfully, but these errors were encountered: