Hello,
after you anlayse run through I have renewed my environment to prevent
other errors.
This is how I proceeded:
(1) Ubuntu 16.04 LTS installed on VMware Workstation
(2) Downloaded the master - branch from Codeface and installed it with
vagrant up
(3) Afterwards I have executed the following commands, so that it runs
sudo apt-get update
sudo apt-get install npm
cd /vagrant/id_service
npm install --no-bin-links
/vagrant/integration-scripts/test_codeface.sh
cd /vagrant
bash shiny-server-pack.sh
/vagrant/id_service/start_id_service.sh&
(4) After that, I did the analysis of qemu, ansible and puppet [1] and
started the webserver
/vagrant/analysis_example.sh
/vagrant/analysis_example_ansible.sh
/vagrant/analysis_example_puppet.sh
cd vagrant;
./shiny-server.sh
(5) After that I could see the projects in the dashboard
http://localhost:8081/apps/dashboard/
Ansible collaboration:
http://localhost:8081/apps/dashboard/?projectid=4&topic=collaboration
Puppet collabortaion:
http://localhost:8081/apps/dashboard/?projectid=6&topic=collaboration
qemu collabortaion:
http://localhost:8081/apps/dashboard/?projectid=2&topic=collaboration
Am 07.04.2017 um 16:41 schrieb Wolfgang Mauerer:
Am 07/04/2017 um 16:33 schrieb Stefan Kuppelwieser:
Actually I tried it with the conway-forreview branch [1] and it worksThe communication analysis can not show anything because no
closly. Now I can enter collaboartion, but I get an mysql-error [2].
It's the same error like the view of communcation [3]. Does the error
occurs because no malinglist has been specified?
communication data have been analysed. We should handle this condition
more gracefully in the web frontend, though, than by just showing an
error that the query failed.
As for the cluster analysis, I suppose you've hit a condition where (for
whatever reason) no clusters are present. Can you select some other
release ranges to see if the problem persists? Unfortunately, I cannot
reproduce the problem because I've analysed a slightly different state
of ansible such that codeface picks slightly different release
ranges.
Please also specify your head revision of your repo so that
I can reproduce the problem locally.
Thanks & best regards, Wolfgang Mauerer
The URL of the colaboration is
http://localhost:8081:/apps/dashboard/?projectid=58&topic=collaboration
Attachment:
puppet-cluster.PNG
Description: PNG image
Attachment:
ansible-cluster.PNG
Description: PNG image
Attachment:
ansible-cluster-correlations.PNG
Description: PNG image
Attachment:
puppet-cluser-correlations.PNG
Description: PNG image