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 would like to be able to add more information to the Gerrit comment that is sent from the Sonar Gerrit plugin. Specifically which project that was tested, through the information from the Sonar report (top component) or a variable provided by the job configuration (Inject environment variables).
Consider the following case; I have a matrix-configured Jenkins job where a different Sonar report is created on each axis combination. As an example, let’s say there are 5 combinations. In the “no SonarQube violations found” case for all 5 combinations, that would mean 5 identical Gerrit comments with the same message “SonarQube violations have not been found.”. I would like the possibility to send this message instead “SonarQube violations have not been found for or ${VARIABLE_FOR_PROJECT}.” for each combination.
[JENKINS-48579] created by softmuppen
The text was updated successfully, but these errors were encountered:
I would like to be able to add more information to the Gerrit comment that is sent from the Sonar Gerrit plugin. Specifically which project that was tested, through the information from the Sonar report (top component) or a variable provided by the job configuration (Inject environment variables).
Consider the following case; I have a matrix-configured Jenkins job where a different Sonar report is created on each axis combination. As an example, let’s say there are 5 combinations. In the “no SonarQube violations found” case for all 5 combinations, that would mean 5 identical Gerrit comments with the same message “SonarQube violations have not been found.”. I would like the possibility to send this message instead “SonarQube violations have not been found for or ${VARIABLE_FOR_PROJECT}.” for each combination.
[JENKINS-48579] created by softmuppenThe text was updated successfully, but these errors were encountered: