I'm using sonarqube for AEM. But when I run mvn sonar:sonar on any module, it shows an error and the project analysis results in failure. Attaching the screenshot for that
I tried upgrading sonarqube too. But I'm not able to do that. Steps mentioned in the sonarqube docs are not quite understandable. Please let me know if there is any solution for this.
Tried upgrading the sonarqube but not able to do that. If that could solve my problem, suggest me how to do that.
Related
I want to use SonarQube for Code Quality analysis. I have Hudson as the CI tool and have integrated clearcase. How do I use SonarQube when the Ant build happens? Do I need to install SonarQube in a server and use a plugin to access it?
Can someone help me?
Install SonarQube web server as a first step. Default port will be localhost:9000.
After installing SonarQube you need to create an Ant target. Sample Script is available on GitHub. If Hudson is working correctly earlier. It will pick up the changes in Ant Script and perform the Analysis. After the completion of Analysis report will be generated and accessible at SonarQube Web Dashboard.
This is how i execute my sonar analysis,
mvn sonar:sonar -Dsonar.issuesReport.html.enable=true
In Sonar 4.0 i was able to generate HTML reports, But in SonarWube 5.6.1 its not working out (No errors thrown)
I have googled a lot and couldn't find an alternate plugin or any fix for this.
If some one can suggest me, that will be helpful
Take a look at SonarLint for Command Line. The functionality was moved there.
EDIT SonarLint for Command Line has been dropped. The recommendation is now to use SonarLint in your IDE or Branch Analysis, which is available in Developer Edition($)
I've completed the atlassian sdk helloworld plugin tutorial, and so far I'm happy that atlas-run shows the plugin.
Import to IntelliJ Idea also went clean.
I understand that Quick Reload plugin is supposed to help avoiding to run time-expensive atlas-run after each minor update.
Could someone please suggest which maven task should be run in order to trigger Quick Reload?
I've tried running: clean, install, deploy from IntelliJ Idea, and each of those crashed Jira.
You can just run "atlas-package" to trigger quick reload.
Best regards,
Michael
I have upgraded my sonar version from sonar-3.2 to sonar-3.5.1 and upgraded sonar-runner from sonar-runner-1.1 to sonar-runner-2.2.2, now when i am deploying project on newly installed sonar 3.5.1 it run successfully and showing ANALYSIS SUCCESSFUL, it also show project name on sonar server when i use localhost:9000 on browser but code is not showing there, no violations are coming etc.
i am using sonar in two ways and both results the same. Two ways are:
1. using sonar standalone through sonar runner from cmd.
2. integrating sonar with Jenkins(1.515) and using maven(3.0.4)
when i do sonar analysis on sonar 3.2 everything is working fine in both of the above cases but problem comes only when i use sonar 3.5.1.
Can anybody help me out on this issue??
Please suggest what would be the possible way to overcome this issue..
your revert will be appreciable.. Thanks in advance!!
Please refer below for logs
and sonar dashboard
So I do confirm that the Sonar Java plugins have been deleted from the extensions/plugins directory and that's why you don't get any measures/violations when analysing a java project. Here is the link to download version 1.2 of the Sonar Java plugin ecosystem : http://docs.codehaus.org/download/attachments/230396085/JavaEcosystem-1.2.zip. You just have to decompress this archive, place all jar(s) in the extensions/plugins directory and relaunch the Sonar server.
I had a project built with maven on a Jenkins CI server, and recently the Sonar portion of the build began to fail with the well known
org.sonar.core.persistence.BadDatabaseVersion: Database must be upgraded. Please browse http://x.x.x.x:9000/setup
I browsed to http://x.x.x.x:9000/setup, and the message there was green and said my database was up to date. The database looks good and the sonar server doesn't throw any Exceptions as far as I can tell from the output, and this installation had been working well up until a few days ago.
I checked that the id was the same between the running server and the database, and insured that only one instance of Sonar was talking to the H2 DB.
My next step is to step through Sonar code, which I'm not eager to do. Any pointers as to what's wrong would be appreciated.
Thanks.
Your Maven plugin version is probably not aligned with your Sonar install.