I'm trying to notify my Slack when a SonarQube analysis has been processed and for that I saw a plugin: https://github.com/astrebel/sonar-slack-notifier-plugin
I followed all the step but I didn't see the slack hook setting in my administration/general view.
You don't mention your version of SonarQube, but that plugin's README clearly states that it is no longer maintained, and implies that it's not compatible above SonarQube 5.4.
Assuming you have a more recent version than that, you should look at the built-in webhooks, which will POST notifications once analysis reports have been integrated.
Related
My organization is using sonarqube:7.1 with sonar-bitbucket-plugin-1.2.3 (https://github.com/mibexsoftware/sonar-bitbucket-plugin) and everything is working fine. We are planning to upgrade to sonarqube:7.5 and while I was testing all the existing plugins, sonar-bitbucket-plugin is causing the issue(It's not supported in the newer version of Sonarqube). I want to upgrade to 7.5+ version of Sonarqube and want sonar-bitbucket-plugin as well. Could someone please help me out?
ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
java.lang.IllegalStateException: Fail to load plugin Bitbucket for Sonar [sonarbitbucket]
This community plugin was relying on the deprecated preview/issues analysis mode to analyze pull requests, that was finally removed.
Since SonarQube 6.7 the support of branches (and then pull requests) analysis has been properly integrated on the server side. Decorating PR was added progressively for various ALM, and for Bitbucket Server it is supported since 7.7.
Note that all branch/PR features are only available in commercial editions (or for free on SonarCloud for open source projects).
I'm trying to update Sonarqube usage to the latest LTS Community version, which at present is version 6.7.5. Prior to the upgrade I have been using sonarqube 5.4 and the Github plugin, and with these when we make Github pull requests the Sonarqube analysis runs in "preview" scan mode and makes comments on the pull request for any issues the scan finds. This setup is largely following this pattern.
However, with the upgrade to 6.7.5 this same flow is no longer working. The Github plugin
"is deprecated, and its functionality more than replaced by the
Developer Edition."
I understand that the Developer version of Sonarqube has pull request commenting built-in, but I have a strong preference to continue using the Community version due to the cost differences. Essentially, something that was once free and part of the open source version seems to have been removed or broken in the latest free and open source version because a similar paid option now exists. So I am trying to find a way to preserve the previous Community version usage with the latest Community Sonarqube version. 6.7.5 Community version runs the Github plugin (even though it the plugin is deprecated), but so far I have been unable to get things to make comments on the Github pull requests.
Is there a combination of parameters/plugins that will allow my 6.7.5 Community version of Sonarqube to analyze and make comments on a Github pull request?
These may be relevant:
https://community.sonarsource.com/t/after-upgrade-to-sq-6-7-5-target-sonar-issues-report-issues-report-light-html-is-not-produced/1921
https://jira.sonarsource.com/browse/SONAR-9770
https://community.sonarsource.com/t/preview-mode-ignored/1234
I believe in my case the issue was that after upgrading the rule sets changed, so the rules I initially thought were being used with 6.7.5 were not in fact being applied. This gave the impression that Sonarqube was not commenting on the pull request and led to my question. But after enabling the rules appropriately I was able to see it comment on GitHub pull requests as expected. So this appears to be a case of user error!
I've asked this question on Gitter, but answer directed me to the documentation I followed.
I'm administrator of TeamCity 2017.2.2 with agents running on Windows 10 (except one on 7). I installed allure-teamcity plugin version 2.6 and added allure tools in version 2.6 as described in the documentation.
The problem is the tool is propagated to the agent on upgrade, but not the plugin itself. Main server shows me the runner I can use as a build step, but once configured none of agents accept this configuration. I've checked agent directory and logs - the plugin is not there and logs doesn't indicate that there was even attempt to pull.
As a holder of commercial license I asked JetBrains technical support, but they told me I need to ask Allure authors. GitHub sends people to Gitter and here, hence the question after unlucky attempt on Gitter.
What do I need to do to get the plugin correctly pulled and working on agents?
Is allure plugin even compatible with TeamCity 2017.2.2?
The problem is that Allure TeamCity plugin looks for a tool called allure-commandline. So you need to make sure that allure-commandline.zip is present in your <TeamCity Data Directory>/plugins/.tools directory.
We have recently migrated to jira agile and the issues have changed from tasks bugs to stories. We have been using maven changes plugin to automatically send notification for new releases and it successfully includes issues resolved and so on. Now that we have stories, it does not include them to the message body. I have updated the configuration properties to include stories also and all possible issue types (Bug, New Feature, Task, Improvement, Sub-task,Story) but still no success. The jira report that is generated by the same plugin is correct but the mail still does not include them.
I also tried to attach the jira report (${basedir}/target/site/jira-report.html) but with no success.
Can anyone propose a solution or a work around too this issue?
After some further research and a lot of code checking in the source code of maven changes plug-in I found out that you have to include the following mapping in your configuration
<issueTypes>
<add>Story</add>
<fix>Bug</fix>
<update>Task</update>
</issueTypes>
This will inform the maven changes plug-in to map the build in xsd add,fix,update to Story, Bug, Task issues that are created with agile jira
I am trying to get commit and author details for a project in sonarqube.
I see scm stats plugin does it for prior versions.
I am using the latest version sonarqube 5.4.
Is there any way we can use scm stats plugin for sonarqube 5.4 or any alternative that i can use?.
Please help.
You can use new SCM functionality offered by SonarQube and no need for SCM plugins.
Go to Administration -- > on left hand side you will see "SCM" option.
For my team , we were looking for SCM report but unfortunately its not available ,so we are using web API to generate it by own.