[
https://issues.apache.org/jira/browse/IGNITE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094094#comment-15094094
]
Pavel Tupitsyn edited comment on IGNITE-2324 at 1/13/16 4:22 PM:
-----------------------------------------------------------------
Findings:
* SonarQube is too complicated to set up on TC, skip it for now
* .FxCop file is an old and inconvenient way of setting up analysis, not
compatible with VS2012+ built-in analyzer. We should configure rule set in
.ruleset file.
* ReSharper inspections are built-in on TC
TODO:
* Set up .ruleset file with relevant rules
* Enable analysis on build so that VS shows warnings during development
* Run separate step on TC with /p:CodeAnalysisTreatWarningsAsErrors that will
fail in case of analysis issues
* Add ReSharper inspections step
was (Author: ptupitsyn):
Findings:
* SonarQube is too complicated to set up on TC, skip it for now
* .FxCop file is an old and inconvenient way of setting up analysis, not
compatible with VS2010+ built-in analyzer. Instead, we should configure rule
set in .ruleset file.
* ReSharper inspections are built-in on TC
TODO:
* Get rid of fxcop file
* Set up .ruleset file with relevant rules
* Enable analysis on build so that VS shows warnings during development
* Run separate step on TC with /p:CodeAnalysisTreatWarningsAsErrors that will
fail in case of analysis issues
* Add ReSharper inspections step
> .NET: Code analysis
> -------------------
>
> Key: IGNITE-2324
> URL: https://issues.apache.org/jira/browse/IGNITE-2324
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> * Investigate code analysis tools (FxCop, SonarQube, etc)
> * Set up a step on TeamCity
> * Set up visual studio to check on build
> * Modify code (adjust inspections/suppressions)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
