Benp/static code analysis radon - #7147
Conversation
4252d8d to
471bd2c
Compare
There was a problem hiding this comment.
This needs to either get picked up as a build artifact or displayed on the console, otherwise you don't ever see the result in an actual build.
E.g. the quality subset for the last commit on the branch.
There was a problem hiding this comment.
Along those lines, have you looked into the --xml option? The documentation suggests that it works with a Jenkins plugin to report them.
There was a problem hiding this comment.
I did glance at that, but didn't consider the plugin. Basically in terms of output, we can get an overall score, or we can get a full report for everything. I had looked at ways of capturing complexity on your diff (can't use diff-quality for it because it considers the whole method/class/etc). But ultimately I thought a straight text report, which includes a total score at the end, would be easiest, esp when thinking of an eventual move to Travis.
9a23914 to
eb4f852
Compare
|
@jzoldak I've adjusted the location of the report so that it's collected after a build. Here's an example: https://build.testeng.edx.org/job/edx-platform-all-tests-pr-flow/822/artifact/reports/code_complexity.log/*view*/ You can see the 'total average' score at the end. We can further filter the report to only provide the total average, but I thought for starters, it may be useful to have the entire report. |
|
@feanil @maxrothman @fredsmith could one of you fellas take a look at adding this library from the DevOps perspective? |
|
👍 from my perspective |
|
👍 from me too. |
|
👍 |
Benp/static code analysis radon
4 participants
No description provided.