Hi, all
After PR 1707 was merged, Sonarcloud now analyze fronted code.
https://github.com/apache/incubator-dolphinscheduler/pull/1707


You can 
open https://sonarcloud.io/dashboard?id=apache-dolphinscheduler for 
more details. There is still much work to do, any contributions are welcome.



------------------ ???????? ------------------
??????:&nbsp;"Java-Chen"<[email protected]&gt;;
????????:&nbsp;2020??1??1??(??????) ????3:43
??????:&nbsp;"dev"<[email protected]&gt;;

????:&nbsp;?????? [discussion] The SonarCloud check in the CI flow



I noticed sonarcloud didn't get the right UT coverage and create PR #1662 to 
fix it.&amp;nbsp;https://github.com/apache/incubator-dolphinscheduler/pull/1662


And updated maven command&amp;nbsp;as below
mvn clean --batch-mode verify 
org.sonarsource.scanner.maven:sonar-maven-plugin:3.6.1.1688:sonar&amp;nbsp; 
-Dsonar.host.url=https://sonarcloud.io -Dsonar.organization=${org} 
-Dsonar.projectKey=${pKey} -Dsonar.login=${token}-Dmaven.test.skip=true can be 
appended to skip tests, it will get 0% UT coverage, but will cost less time on 
local testing .


For now, Sonarcloud just analysis Java source file. There are still need some 
work to get fronted code be analyzed. When the work is done, I will infrom it.


------------------&amp;nbsp;????????&amp;nbsp;------------------
??????:&amp;nbsp;"nauu"<[email protected]&amp;gt;;
????????:&amp;nbsp;2020??1??1??(??????) ????0:04
??????:&amp;nbsp;"[email protected]"<[email protected]&amp;gt;;

????:&amp;nbsp;Re: [discussion] The SonarCloud check in the CI flow



Thanks for your reply, this is normal discussion, no need to apologize.

I will try the test way in local environment , if there is any problem, i will 
continue to follow up in this mail.

However, I still feel that the method of local testing is too complicated. Such 
as UT coverage , checkstyle and spotbugs,&amp;nbsp; If the rules are clear, 
these checks are easy to do in the IDE.

BTW, I said causeing merge to slow do not means we should not use SonarCloud. 
SonarCloud is very useful.
But If the rules are clear, and there is a way for local testing, we can get 
everything right before pull request, instead of trying.



[email protected]
zhukai/nauu ygsoft




&amp;gt; On Dec 31, 2019, at 11:37 PM, ?????? <[email protected]&amp;gt; 
wrote:
&amp;gt; 
&amp;gt; Sorry for your confuse 
&amp;gt; 
&amp;gt; 1. SonarCloud's test standards
&amp;gt; For now , SonarCloud use the default Quality Gate analysis new code. 
if one of these conditions is true, Quality Gate will failed .
&amp;gt; 
&amp;gt; For SonarCloud's testing standards, You can check here :
&amp;gt; https://sonarcloud.io/organizations/apache/quality_gates/show/9
&amp;gt; 
&amp;gt; More metric definitions:
&amp;gt; https://sonarcloud.io/documentation/user-guide/metric-definitions/
&amp;gt; 
&amp;gt; 2.&amp;nbsp; Test in a local development environment
&amp;gt; Use&amp;nbsp; maven&amp;nbsp; command will be a easy way , 
there&amp;nbsp; 2 steps:
&amp;gt; 1) Sign up at https://sonarcloud.io/ <https://sonarcloud.io/&amp;gt; , 
set up organization, projectKey, and token
&amp;gt; 2) Run maven command locally , remember replace the variable as you 
set up at step 1)
&amp;gt; mvn clean --batch-mode verify 
org.sonarsource.scanner.maven:sonar-maven-plugin:sonar 
-Dsonar.host.url=https://sonarcloud.io -Dsonar.organization=${org} 
-Dsonar.projectKey=${pKey} -Dsonar.login=${token}
&amp;gt; Then your can browse analysis&amp;nbsp; at SonarCloud.
&amp;gt; 
&amp;gt; 3. Cause merge to slow
&amp;gt;&amp;nbsp; Adding SonarCloud check in the CI workflow means developers 
need spend more time on code implementation&amp;nbsp; stage ,but less on 
testing and debuging. I think it's worthy .
&amp;gt; 
&amp;gt; 
&amp;gt; ------------------ Original ------------------
&amp;gt; From: "nauu"<[email protected]&amp;gt;;
&amp;gt; Date: Tue, Dec 31, 2019 10:36 PM
&amp;gt; To: 
"[email protected]"<[email protected]&amp;gt;;
&amp;gt; Subject: [discussion] The SonarCloud check in the CI flow
&amp;gt; 
&amp;gt; Hi :
&amp;gt; 
&amp;gt; I'd like to discuss the SonarCloud check in the CI flow, It makes me a 
little confused.
&amp;gt; 
&amp;gt; Before this, we have a very clear goal in our project:
&amp;gt; The root issue #1460,&amp;nbsp; It defines the overall goal and break 
into subtasks. Such as [Add unit test] #1465, It defines which unit tests 
should we write and what is the coverage ratio.
&amp;gt; 
&amp;gt; But now,&amp;nbsp; SonarCloud suddenly added in without discussion in 
the community(dev maillist).It is obviously unstable,&amp;nbsp; and causing the 
progress of the merge to slow.
&amp;gt; 
&amp;gt; I'm not quite sure what is the SonarCloud's testing standards, what is 
our goals, and how to test in a local development environment.
&amp;gt; 
&amp;gt; 
&amp;gt; [email protected]
&amp;gt; zhukai/nauu ygsoft
&amp;gt; 
&amp;gt; 
&amp;gt; 
&amp;gt; 
&amp;gt;

Reply via email to