Type: New Feature
Affects Version/s: None
Fix Version/s: None
Like we do for the Travis Add-on or the VSTS tasks, Jenkins users would expect our plugin to feed the branch and PR properties automatically when it's appropriate - in order to not have to learn them.
To get the information, we could rely on https://jenkins.io/doc/book/pipeline/multibranch/#additional-environment-variables then pass them to the scanner.
That should be fairly easy with the SONAR_SCANNER_PARAMS environment variable.
Obviously, it should still be possible to force them - which is possible when using CLI params.
Seems there are some standard variables provided by this plugin:
CHANGE_ID is documented here: