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
While configuring the Sonarqube in pre-build stage , it fails to retrieve the sonar token variables and bugs out in the ci steps. The Sonarqube global token is already supplied in the input variables and project key is also present.
👟 Reproduction steps
Go to either of the plugin Sonarqube or Sonarqube 1.0.0 or v1.1.0.
Enter the project key , apikey , endpoint
Use properties file = choose any
Check for sonaranalyis = true
Abort on policy check = false
Container image = blank (default)
👍 Expected behavior
It should fetch the proper variables , run the sonarscanner and show the results in Sonarqube dashboard and complete the ci step.
👎 Actual Behavior
Fails with errors of missing variables whereas they are already present
☸ Kubernetes version
EKS Kubernetes 1.29 and Devtron v1.2.2
Cloud provider
AWS ap-south-1
🌍 Browser
Chrome
🧱 Your Environment
Tried running Sonarqube 9.9 LTS community and also 2025 latest both had same issue.
Sonarqube addition in helm in devtron stack manager also didn't work
Tried adding the option to run the scanner container manually in a custom CI task and mounted the code accordingly and it failed with permission denied error.
✅ Proposed Solution
To fix, there could be a change in SONAR_LOGIN which is getting deprecated and SONAR_TOKEN should be read from variables.
👀 Have you spent some time to check if this issue has been raised before?
Hi @tanmaymohan, thanks for raising the bug. I attempted to replicate it and encountered the same issue. However, I'm not sure if changing to SONAR_TOKEN will resolve it. Tagging @abhibhaw for his thoughts on this.
Another thing I tried with discord support from devtron was to run the ci in sleep() and then by directly running the commands from that container (somewhat like sshing to container). Only then it worked.
Hey @tanmaymohan can you please help me with the logs of your CI execution where sonarqube fails (please be sure to remove any sensitive details before sharing)
📜 Description
While configuring the Sonarqube in pre-build stage , it fails to retrieve the sonar token variables and bugs out in the ci steps. The Sonarqube global token is already supplied in the input variables and project key is also present.
👟 Reproduction steps
Go to either of the plugin Sonarqube or Sonarqube 1.0.0 or v1.1.0.
Enter the project key , apikey , endpoint
Use properties file = choose any
Check for sonaranalyis = true
Abort on policy check = false
Container image = blank (default)
👍 Expected behavior
It should fetch the proper variables , run the sonarscanner and show the results in Sonarqube dashboard and complete the ci step.
👎 Actual Behavior
Fails with errors of missing variables whereas they are already present
☸ Kubernetes version
EKS Kubernetes 1.29 and Devtron v1.2.2
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
Tried running Sonarqube 9.9 LTS community and also 2025 latest both had same issue.
Sonarqube addition in helm in devtron stack manager also didn't work
Tried adding the option to run the scanner container manually in a custom CI task and mounted the code accordingly and it failed with permission denied error.
✅ Proposed Solution
To fix, there could be a change in SONAR_LOGIN which is getting deprecated and SONAR_TOKEN should be read from variables.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: