Actions
action #156091
open[timeboxed:6h] Use codescene for finding knowledge islands and complex code size:S
Start date:
2024-02-26
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
https://codescene.com/ can be used for free with open source projects to analyze the code.
Features:
- Finding knowledge islands
- Calculate code complexity
- Simulate a person leaving a team
- Show which files are very likely to be changed in the same commit
- Same for subroutines
- Create goals and check code health in PRs
We should consider using this for our projects.
- I created an example project for os-autoinst and can give a short demo.
- example project for openQA
- example project for qem-bot
Acceptance criteria¶
- AC1: Reports have been analyzed and follow-up tasks created
Suggestions¶
- Review the existing "example projects" reports and derive potential points of improvements
- Consider alternative options which are free software
Updated by tinita 3 months ago
- Description updated (diff)
I tried to add openQA to the project (there can be more than one repo per project). Data appeared to be broken after the analysis ran. I removed openQA from the project again, restarted analysis and it still looked broken.
So I deleted the project and created a new one with only os-autoinst. Updated the URL.
Updated by tinita 3 months ago
- Description updated (diff)
Apparently the first analysis after the project creation works.
If I trigger a new analysis, data is broken.
Compare:
- First run: https://codescene.io/projects/50439/jobs/2093641/results?scope=month#code-health
- Next run: https://codescene.io/projects/50439/jobs/2093684/results?scope=month#code-health
But this way I now created an openQA project as well:
https://codescene.io/projects/50441/jobs/2093692/results?scope=month#code-health
Actions