Am 05/04/2017 um 12:22 schrieb Stefan Kuppelwieser:
Am 26.03.2017 um 23:21 schrieb Wolfgang Mauerer:
Am 24/03/2017 um 20:10 schrieb Stefan Kuppelwieser:I have tried it with an empty list of revision [1] and it works.
after I run the qemu example I want create two new example for thethat's indeed an under-documented edge of codeface. Basically,
repository ansible[1] and puppet[2].
I create following file structure the new analysis
|-/vagrant (folder)/
|-- analysis_example_ansible.sh
|-- analysis_example_puppet.sh
|---/conf (folder)/
|---- ansible.conf
|---- puppet.conf
After I found no documentation to create a new analysis, I used the
example as a template.
to perform a time-resolved analysis, we have to flatten the revision
graph of a project, and then traverse it. This can either be
done by specifying a list of key releases along which the history should
be traversed, or by specifying no revisions at all, in which case
the commits are ordered by time, and the list of commits is
traversed in six-month intervals. As the qemu example shows,
we can also include release candidate versions; a time interval is then
composed of three dates:
[start, rc, end]
where rc must lie within [start, end], and denotes the first release
candidate version in a development cycle. The RCs should usually
not be specified as part of the revisions list, because they are not
full releases.
Using explicit tags works well for well-tended projects, or when the
regularity of cutting releases and the comparability of different
development cycles is of interest. When the release structure is
irregular (which I assume from a cursory glance at puppet and
ansible is the case for these), I would use time-based analysis. Just
specify an empty list of revisions and rcs in your config file,
and codeface will automatically segment the development history into
intervals.
The analysis runs through.
Unfortunately, it works only partially.
It is possible to see the overview [2] of a project, but if I want to
view the details of a the collaboration I get an JavaScript Error [3].
As well I get an error at viewing the communication.
For the reason I tried it with another project qemu and openssl as well,
but unfortunately get the same error.
[1]:
https://github.com/StefanKuppelwieser/Codefacee-analysis/tree/master/conf
[2]: JavaScriptErrorConsole
[3]: JavaScriptError.txt and JavaScriptErrorConsole.PNG
