140 likes | 301 Views
Diligent feedbacks. Andrea Manieri. For build. For deployment testing. For documentation generation. Conclusions. Diligent build Status. Statistics on Build Strongly needed, so done!. 5 di 5. Build Feedbacks. To be understood any implication on confidential code
E N D
Diligent feedbacks Andrea Manieri
For build For deployment testing For documentation generation Conclusions
Diligent build Status • Statistics on Build • Strongly needed, • so done! 5 di 5
Build Feedbacks • To be understood any implication on confidential code • Strict related to the possibility to have Commercial or critical projects building with ETICS • The only solution is to run build on your machines or install ETICS sw on your own machines? Not so exiting! • The license compatibility automatic check (not in ETICS TA) • In DILIGENT we have several licenses : Mostly Apache 2.0, Many LGPL, One GPL, Some other OS like (CDDL, BC LA, BSD), One commercial. • ENG is going for master thesis on this topic 1 di 5
For build • For deployment testing For documentation generation Conclusions
Deployment Testing status • To ensure DILIGENT software is deployable and report on it • Identify the configuration to be tested: • functionalities > services > ETICS build modules • gather deployment dependencies • Model the identifies configuration into ETICS: • one ETICS deployment module for each DILIGENT service • configuration of the modules dependencies • Test if all modules are deployable • Report all problems found in Savannah
Deployment Testing status (II) • All modules/scripts in - “deploytest” subsystem • DILIGENT services modules: • one module for each service to be tested describing the service specific information • Generic deployment script: • copies the libraries to the right place • starts the container • downloads the WSDL file • stops the container
Deployment Testing Feedbacks • Progressive availability of ETICS clients functionalities • Functionalities Release plan would be useful • Lack of rigorous documentation • Full and expert support by ETICS team • Clients usability need be improved and aligned • ETICS scheduler to periodically execute etics-* commands • Report generation: I)fully automatic ii) also available in local execution • Authorization I) at command level (not configuration level) ii) in webapp user lost on which permissions/roles 1 di 5
Deployment Testing Feedbacks (II) • CLI • Simple to use (easy to learn how to work) • Good the use of templates • [problem] No interactive execution required done? • WebApp • User-friendliness I) Navigation sometimes is not so intuitive than expected ii) Compatibility with different browsers is useful • Usage of templates as in CLI • Solved issues: I)Session expires too quickly ii) Set dependencies (solved) 1 di 5
For documentation generation For Build For deployment testing Conclusions
API doc status • Added a script for running javadoc for each configuration • Initially, useful a report on “how many configurations have such script
Conclusions For Build For deployment testing For API documentation
(my personal) Conclusions • Not all Communities feedbacks are ETICS requirements! • Usability and Accessibility for Users. YES! • Reporting and Monitoring facilities for Managers. YES! • Confidentiality and … Accounting capabilities. YES, in ETICS 2! • [suggestion] provide questionnaire-based Survey to all final users to have an overall assessment • [suggestion] improve the usage of Savannah by end-users 4 di 5
Thanks! (Any feedback on this presentation layout?)