We’re using sonarqube developer edition Version 8.1 and trying to enable PR decoration. we cannot establish a SonarQube PR scan without the pull request’s CHANGE_ID.
Logic would work as follows:
Jenkins detects changes to a particular branch
Start Jenkins build
If branch is as PR the CHANGE_ID should be pull request id (number)
If branch is not a PR the CHANGE_ID should be null
The CHANGE_ID is not configured in our Jenkins environment, is there a way to configure PR decoration in Bitbucket without manually configuring the fields in Jenkins ??
Pull request analysis and decoration is part of Developer Edition, which you said above you already have. So the question is why you’re having problems getting going with it.