[ANN] SonarQube 5.3 RC2 is now available

[Fabrice Bellingard]

Hi SonarQube Community,

Here is the second release candidate of SonarQube 5.3 that fixes some bugs reported on RC1.

As usual, here are the useful links to help test further:

• Original announcement: https://groups.google.com/d/msg/sonarqube/jrVFdVvgh6Q/D8cBDhc9BAAJ
• Download: https://sonarsource.bintray.com/Distribution/sonarqube/sonarqube-5.3-RC2.zip 
• Release notes: https://jira.sonarsource.com/jira/secure/ReleaseNote.jspa?projectId=10930&version=11647
  
• Staging Documentation: http://docs.sonarqube.org/display/SONARNEXT/Documentation
• Upgrade notes: http://docs.sonarqube.org/display/SONARNEXT/Release+5.3+Upgrade+Notes

Thanks to the early testers for their first feedback on RC1!

Best regards,

Fabrice BELLINGARD | SonarSource SonarQube Platform Product Manager http://sonarsource.com

[Jorge Costa]

Hi Fabrice,

i was playing with rest api to create rules from templates, i notice 2 things:

1. the markdown seems to be broken, ** results in italic instead of bold and mentioned in the help.

2. also the delete rule using both rest and web interface does not clean the entry in database. if trying to recreate the same rule but with different markdown i will return the markdown from the first time i created the rule. i am ensure if this is only of this version. but looks that its broken

br,

jc

[Jorge Costa]

for 2, seems that is a feature. at least if specifing prevent reactivation it should fail to create rule. so it seems db will always contain all rules created over time. would be good to actually be able to delete it

[Jorge Costa]

Hi,

a bit more feedback:

1. would be nice that on the new project key available in some place in the home page of the project, in similar way as the description widget that still exists in the custom widget

2. ive been playing with service api/quality_profile/add_project and looks its working a bit weird.

curl -u admin:admin -X POST http://localhost:9000/api/qualityprofiles/add_project?profileKey=complete?projectKey=ProjectKey => {"errors":[{"msg":"Either projectKey or projectUuid must be set"}]}

the services change_parent and copy use same post notation and are ok. if instead of using the url, i add the parameters as content then i am able to assign the project to the profile but i receive a HttpStatusCode.NoContent instead of HttpStatusCode.Ok. this happens in both 5.2 and 5.3

Br,

Jorge Costa

[davidb...@gmail.com]

I tried upgrading from SonarQube 5.2.
I followed the steps outlined here: http://docs.sonarqube.org/display/SONARNEXT/Upgrading (i.e. stop sonar service, backup mysql db, unzip new build, etc.)

After unzipping 5.3-rc2 and making required changes to sonar.properties and copying previous plugins (sonar-cxx-plugin-0.9.4, sonar-java-plugin-3.6, sonar-jira-plugin-1.2, sonar-scm-git-plugin-1.1, sonar-scm-svn-plugin-1.2) and starting everything up and going to <sonarqube url>/setup and migrating the database successfully, I get some odd results.

The dashboard displays correctly but if I try to go to a project page it never displays (the round working icon just rotates endlessly).
I figured that I had to analyze the project again, so I ran my jenkins job (that uses the sonar plugin). But the job failed on the sonar plugin:

ERROR: Error during Sonar runnner execution
org.sonar.runner.impl.RunnerExecption: Unable to execute sonar
...
Caused by: java.lang.IllegalSTateExecption: Unable to register extension org.sonar.plugins.java.JavaSquidSensor
...
Caused by: java.lang.NoClassDefFoundError: Lorg/sonar/api/checks/NoSonarFilter;
...
Caused by: java.lang.ClassNotFoundExeception: org.sonar.api.checks.NoSonarFilter
...

If I put everything back the way it was (i.e. SonarQube 5.2 and restore my db) everything works fine (I can navigate to sonar project pages and see stuff, jenkins sonar plugin runs fine, etc.).

Also, when the jenkins sonar plugin fails it prints the build command (sonar-runner -e ...) which has the user/password in plain text in the jenkins log, which I don't like. Is there a way to hide that or use a token with the jenkins plugin?

[Sebastien Lesaint]

Hello Jorge,

My 2 cents for point 2: the URL is invalid. It contains two "?". The second one should be a "&", right?

Regarding point 1: ticket SONAR-7167 has been opened.

Sébastien LESAINT | SonarSource
Platform Developer

http://sonarsource.com

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/9958250d-19d1-467e-9483-61667fc3e52d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jorge Costa]

Hi Sebastien,

i might made a typo & should be correct indeed, i will double check. thanks for the reply.

br,

Jorge Costa

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/CAAiZAQyc9sCo2C%3DCa-ZDFu-cMD8PQ1_mc-_nLkEnSjQ-LX68uQ%40mail.gmail.com.

[Teryk Bellahsene]

Hi Jorge,

Concerning point n°1 ticket created: https://jira.sonarsource.com/browse/SONAR-7211

[jackie...@gmail.com]

hi David, I am having the same issue with jenkins (IllegalSTateExecption..JavaSquidSensor...NoSonarFilter.. etc), did you manage to solve it?

[jtie...@gmail.com]

I had the same error with sonar-java-plugin-3.6 and sonar-scm-git-plugin-1.0 when running the sonar analysis on SonarQube 5.3. After upgrading both to the latetst (3.10 and 1.1 at the current time of writing) the issue went away. Also don't forget to restore the default java quality profile in order to get the newly introduced rules in the releases since 3.6 in your analysis result.