-
Notifications
You must be signed in to change notification settings - Fork 47
Version control support
Silvio Montanari edited this page Aug 29, 2017
·
1 revision
code-forensics currently supports only git and subversion. Unfortunately subversion cannot produce the detail of information in its log output that is required by Code Maat and in turn code-forensics to perform all the analyses. Below is a list of what can be expected to (or not to) work depending on the VCS type.
| Code Maat analyses | git | subversion |
|---|---|---|
| revisions | ✅ | ✅ |
| soc | ✅ | ✅ |
| coupling | ✅ | ✅ |
| authors | ✅ | ✅ |
| main-dev | ✅ | 🚫 |
| entity-effort | ✅ | ✅ |
| entity-ownership | ✅ | 🚫 |
| communication | ✅ | ✅ |
| absolute-churn | ✅ | 🚫 |
| entity-churn | ✅ | 🚫 |
| code-forensic analyses | git | subversion |
|---|---|---|
| hotspot | ✅ | ✅ |
| commit message | ✅ | ✅ |
| sloc trend | ✅ | ✅ |
| complexity trend | ✅ | ✅ |
| sum of coupling | ✅ | ✅ |
| temporal coupling | ✅ | ✅ churn metrics will not be available |
| developer coupling | ✅ | ✅ code ownership report will not be available |
| developer effort | ✅ | ✅ |
| knowledge map | ✅ | 🚫 |
| system evolution | ✅ | ✅ churn diagram will not be available |