-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonar CNES Report Generation Fails When Utilizing Jenkins Global Env Var #340
Comments
Hi, sorry for the late answer, it appears that your workaround is not efficient and the plugin stop because it detect an unsupported SQ version. If this issue is still a problem to you, I can for the moment only advise you to look to the compatibility table and download the correct version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Encountering branch not found error when Sonar CNES report generation utilizes the BRANCH_NAME Jenkins global environment variable.
Environment:
Sonar CNES Report version 4.1.1 with SonarQube server 9.4 (a recommended workaround has been added to get these two versions to work together).
This error was found while using the following combination of services: Bitbucket, Jenkins, SonarQube w/ PR Decorations enabled, Sonar CNES Report tool and using the Jenkins BRANCH_NAME global env var for the --branch option.
i.e.
java -jar <cnes-report-jar-file> -t <sonarqube-token> -s <sonarqube-url> -p <project-name> -b ${env.BRANCH_NAME}
Steps to Reproduce Error:
And here is the actual error that results in Jenkins:
I've been thinking about how this could be resolved. It doesn't seem like Bitbucket nor Jenkins should change their naming system in this case. It also doesn't seem like SonarQube should change their naming system for PR branches since it doesn't look like their API provides any meaningful data for the Sonar CNES Report tool to use for a PR branch anyways.
In short, it seems like these PR branches may not be useful for generating a CNES report; as such, I thought it would make sense to reach out here to see if there was a way for PR branches specified in the --branch option to be handled/ignored by the Sonar CNES Report tool?
Thanks in advance!
The text was updated successfully, but these errors were encountered: