Curious alert posted on analysis page

Report a bug
#1

  • versions used: SonarQube-8.4.2 D.E., Sonar Plugins:
    $ ls -1 $SONARQUBE_HOME/extensions/plugins
    backelite-sonar-swift-plugin-0.4.6.jar
    checkstyle-sonar-plugin-4.29.jar
    java-i18n-rules-0.1.0.jar
    README.txt
    sonar-cobertura-plugin-2.0.jar
    sonar-csharp-plugin-8.1.0.13383.jar
    sonar-css-plugin-1.1.1.1010.jar
    sonar-findbugs-plugin-3.11.1.jar
    sonar-flex-plugin-2.5.1.1831.jar
    sonar-go-plugin-1.6.0.719.jar
    sonar-groovy-plugin-1.6.jar
    sonar-html-plugin-3.2.0.2082.jar
    sonar-jacoco-plugin-1.1.0.898.jar
    sonar-java-plugin-6.3.2.22818.jar
    sonar-javascript-plugin-6.2.0.12043.jar
    sonar-kotlin-plugin-1.5.0.315.jar
    sonar-php-plugin-3.3.0.5166.jar
    sonar-pmd-plugin-3.2.1.jar
    sonar-python-plugin-2.5.0.5733.jar
    sonar-ruby-plugin-1.5.0.315.jar
    sonar-scala-plugin-1.5.0.315.jar
    sonar-scm-git-plugin-1.9.1.1834.jar
    sonar-scm-svn-plugin-1.9.0.1295.jar
    sonar-softvis3d-plugin-1.1.0.jar
    sonar-typescript-plugin-2.1.0.4359.jar
    sonar-vbnet-plugin-8.1.0.13383.jar
    sonar-webdriver-plugin-1.0.5.jar
    sonar-xml-plugin-2.0.1.2020.jar
    sonar-yaml-plugin-1.5.1.jar

  • error observed
    Project analyzed displays error message:

    PR warning
    PR warning1095×557 24.3 KB

No indications of any issues in ce.log:
ce_udf-model-schema.log (8.2 KB)

#2

Hi,

Which ALM?

 
Ann

#3

GitHub
Sorry, I cannot provide a repeatable example project.

#5

Hi @Jaff,

Do you mind being more explicit about your report? Did the PR decoration actually worked?

I’ve noticed Pull Request decoration | status=SUCCESS in the log, hence my question.

Cheers

#6

Philippe,
Yes. PR decoration was visible in the GitHub page:

Screen Shot 2020-09-25 at 3.57.19 PM
Screen Shot 2020-09-25 at 3.57.19 PM1878×1026 123 KB

Warning still displays on the analysis page.

#7

Can you provide us with a view of this project settings, especially the Pull request decoration tab? I’m mainly interested by the value of the Repository identifier field.

#8

pull-request-decoration_tab
pull-request-decoration_tab1292×792 60.3 KB

#9

As mentioned in the warning message, I think your Repository identifier should contains the organization slug too: org/rpo.

This is also mentioned here:

image

What’s weird to me is that I would expect the PR decoration to fail without the proper repository identifier. I’ll dig a bit further.

#12

Hi @Jaff, I’ve tried to reproduce and the PR decoration definitely can’t work without the organization slug being part of the repository identifier.

Could you fix the repository identifier and keep us inform on how it impacted your PR decoration?

#13

Those settings are definitely present; although sometimes on first analysis of a new project they are absent, I have observed. What might be the solution for that situation?