Hey folks,
I can reproduce this issue: it seems to be related to targeting a SonarQube v6.7 instance (it works fine against a SonarQube v7.9 instance). I’ve reported this internally, and will keep you updated.
Colin
Hey folks,
I can reproduce this issue: it seems to be related to targeting a SonarQube v6.7 instance (it works fine against a SonarQube v7.9 instance). I’ve reported this internally, and will keep you updated.
Colin