Welcome to the SonarSource Community!
The SonarSource Community is a collaborative forum where SonarSourcers and community users of SonarSource products post every day. You’ll find detailed articles and technical discussions that cover the most common use-cases, and some tricky ones. It’s a great resource for your team to gain knowledge about our products and more generally about code quality and security.
This is a shared community resource — a place to share skills, knowledge and advice. Treat it like one!
Then please do add it to that thread.
If the thread is still relatively new and unsolved, your additional details may help point to the root cause. Please add them!
If the thread is older than 2 months, you should create a new thread that includes all your own details. A lot can change in 2 months, and simply “me too”-ing on an old thread doesn’t help anyone help you. But do reference any existing threads that seem relevant.
- This forum is organized in different categories, covering the most common requests you may have. Make sure to choose carefully, to maximise your chances to get the attention of interested people.
- The pinned topic in each category is here to help you to better understand what we expect to see in each of them, and often detail the appropriate format for your post.
Most of the time, your question will deserve a new topic, containing information specific to your situation. If many topics should be consolidated into one, we’ll take care of it! In addition…
- Do not bump old posts and try to tag-on with a possibly related issue.
- Do not divert a topic by changing it midstream
Provide as much detail as possible. What are you trying to do, what have you tried, and what hasn’t worked? Dumping logs and calling it a day won’t get you much attention.
- A meaningful title
- Helpful tags (if you’re having trouble analyzing Java code, add the
javatag). However, more is not necessarily better
- A well formatted post is more likely to get attention.
- Make sure to provide as much context as possible for users to understand your ask
- For any technical issue provide logs, version numbers, steps to reproduce
- Always share what investigations were performed already and/or which content you’ve already consulted
When possible, we prefer that users share code/logs publicly, redacted as necessary, so that all users can benefit from these interactions in the Community. Our default is transparency.
However, sometimes it’s just not reasonable to post all the necessary material publicly, or even to redact it. In such cases, SonarSourcers may agree to accept your code or logs privately for further troubleshooting. You can tell who SonarSourcers are by the Sonar “waves” placed over their avatars.
Commercial users of SonarQube (Developer Edition, Enterprise Edition, Data Center Edition) can refer to the SonarSource Terms and Conditions for specific provisions related to confidentiality.
SonarCloud users can similarly refer to the SonarCloud Terms of Service.
Every organization will have its own standards for redacting/sharing information, and we suggest all users follow them. We are not responsible for code or logs shared with non-SonarSourcers.
We expect you to have taken a look at product documentation, and have searched around for an answer before posting. For instance, common issues are often described in our Community Guides.
The topics discussed here matter to us, and we want you to act as if they matter to you, too. Be respectful of the topics and the people discussing them, even if you disagree with some of what is being said.
- Be civil. Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.
- Be respectful. Don’t harass or grief anyone, impersonate people, or expose their private information.
- More than that, be kind. Everyone has something they don’t know much about. Everyone needs help sometimes. And everyone makes mistakes. Give the kinds of responses you would like to get.
- Constructive criticism is welcome, but criticize ideas and product features, not people.
- Keep it clean. Don’t post anything obscene or sexually explicit.
- Respect our forum. Don’t use hate speech or images. Don’t post spam or otherwise vandalize the forum.
These are not concrete terms with precise definitions — avoid even the appearance of any of these things. If you’re unsure, ask yourself how you would feel if your post was featured on the front page of the biggest newspaper in your country (e.g. the New York Times).
This is a public forum, and search engines index these discussions. Keep the language, links, and images safe for family and friends.
This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.
- Wait a few days before bumping a topic that hasn’t received a response.
- Do not @name mention individuals not involved in the topic.
- Contribute to the community (helping others) as much as you expect to receive help.
- If you need SLAs, guaranteed response, privacy, SonarSource also offers Commercial Support.
@name mentioning is when you type someone’s username with an
@ preceding it. Doing this sends a notification to the user. Depending on their settings, it may also send them an email message.
In general, it is considered bad form to @name mention someone not already engaged in the conversation. Please don’t do it.
It can be annoying
- Active people who were being frequently mentioned in topics were first to request that this practice be minimized. Some people may not mind being mentioned, but we’d still like to limit the number of notifications these folks get.
- @name mentioning a user will often send them an email. Abuse of this feature can fill up someone’s email inbox.
- Some community members feel that too much unsolicited pinging discourages them from participating in the long-run. It can be overwhelming to be on the hook to reply to any and all follow-up.
It is often unnecessary
- Active users often get notifications of new posts and watch the site regularly anyway.
- Posting to the best category with a descriptive title will usually get your topic more attention than mentioning specific users.
- In general, this community prefers to keep discussions focused on ideas and not individual users . If you do not feel your post has received the attention you’d like, we encourage you to reformulate it rather than call in specific people.
Yes! We just ask you to use it thoughtfully and sparingly. Some good uses of @name mentioning:
- To clarify who you are responding to, in a conversation that has multiple participants
- To give credit to someone from whom you learned the information you are passing on
Moderators have special authority; they are responsible for this forum. But so are you. With your help, moderators can be community facilitators, not just janitors or police.
When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. Just flag it. If enough flags accrue, action will be taken, either automatically or by moderator intervention.
In order to maintain our community, moderators reserve the right to remove any content and any user account for any reason at any time. Moderators do not preview new posts; the moderators and site operators take no responsibility for any content posted by the community.
You may not post anything digital that belongs to someone else without permission. You may not post descriptions of, links to, or methods for stealing someone’s intellectual property (software, video, audio, images), or for breaking any other law.
New users (no more than 1 post, made 60 days ago or less) can delete their own accounts from their user preference page. Other users should email email@example.com to have their accounts anonymized. Please include your site username in the request.
Yes, legalese is boring, but we must protect ourselves – and by extension, you and your data – against unfriendly folks. We have a Terms of Service describing your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our TOS.