Closed jdevoo closed 6 years ago
Are you passing a layerGroup
parameter? If not, that probably explains the first message No layer group parameter specified...
The other log entries relate to a problem when code-forensics invokes code-maat. The message basically is the direct output of the code-maat program and what that means is that code-maat cannot parse the log input that it's being given. That could be because the log file is malformed for whatever reason, although it shouldn't happen as long as the git log command executes correctly. It could also happen because a log file for a particular time period is empty (and that depends on the activity on the repository) but again the last version of code-forensics should have rectified this behaviour.
I don't have much time until next week to take a deeper look at this, in the meantime here are a few tips to help you troubleshooting.
Inspect the log files that code-forensics generates (they are stored in the configured temp directory, default ./tmp
) to spot any possible anomalies.
Run code-forensics passing the environment variable COMMAND_DEBUG
to enable more verbose logging, e.g.:
COMMAND_DEBUG=true gulp system-evolution-analysis ...
. This will display the exact script commands that are used to execute the git and code-maat programs, so you could run them manually, again to check for any anomalies.
I am sorry - had missed that parameter in my notes. The other issue was with my malformed gulpfile above - layerGroups at the wrong level. The debug hint will help me as well. Closing this for now as I have not spent much time with code maat itself. Thank you!
I have tried a system-evolution-analysis on alfresco-repository using the following gulpfile.js
dateFrom is 2010-01-01 and dateTo is 2017-12-31 but it shows this in the logs...
I checked the doc but not sure what I missed...
I also notice the following entries in the log from this analysis - what are these related to?
Invalid CodeMaat output: >>This is Code Maat, a program used to collect statistics from a VCS.