Release BETA Integration Tool Status Geneva – 1 March 2007 Paolo Fabriani paolo.fabriani@eng.it
Release BETA Meeting - Geneva, 1-2 March 2007 Summary Improvements foreseen for release Beta: ETICS Build System Build/Test Reports Web Application Distribution Web Application Release BETA Meeting - Geneva, 1-2 March 2007
The ETICS Build System Features and Improvements Some (current and future) ETICS features would improve the current build and test activity in DILIGENT: Available: Parallel Remote Builds and Multiple Platform support Package Repository and Report Browser with improved GUI Some software measures are currently computed at each build. More measures are expected to be introduced ... Planned: Co-Scheduling (useful for remote test) Automatic Unit Test Execution & Reporting Improved reporting based on Disseminators (aggregators, transformers, format converters, ...) All the above functionalities assume web-based access to results (build/test reports, packages, metrics reports, ...) Release BETA Meeting - Geneva, 1-2 March 2007
The ETICS Build System DILIGENT Constraints License Issue in DILIGENT: It was initially expected to be solved for BETA release That’s no longer true: source and binaries must stay confidential until FINAL release So, ETICS (as it is now) cannot still be exploited fully ... The adoption of private resources solves the confidentiality of source code, but ETICS Package Repository and Report Browser still have unrestricted access ... unless ETICS allows to disable guest access An official list of requirements to ETICS team is expected by the end of March Guest user disabling will be given high priority Release BETA Meeting - Geneva, 1-2 March 2007
Build Report Web Application Improvements for BETA Issue: the Build Report page has been very useful to developers, but requires continuous Eng effort to: submit istantaneous build schedule nightly builds Improvement: Istantaneous build functionality will be provided to authorized users The functionality will be made available on best-effort basis Development and Support to Build will have Highest Priority Release BETA Meeting - Geneva, 1-2 March 2007
Distribution Web Application Report on Alpha Alpha Release Components grouped by Service and by Area (e.g. CL, PM, etc...) Component published as tgz Published links to README (already in vcs modules but not packaged) API documentation Available at http://grids16.eng.it/diligent/download/alpha Access Control Based on X.509 certificates (so mainly limited to developers) It would be good to use the same access control system for the WA and the Portal Release BETA Meeting - Geneva, 1-2 March 2007
Distribution Web Application Improvements and changes for BETA HEAD Version Same web application used for Alpha, but pointing at the latest development version Available at http://grids16.eng.it/diligent/download/HEAD Beta Release Distribution of...? Components’ TGZ ServiceArchives Links to documentation README (shall we have them for ServiceArchives?) API documentation (probably project-wide) Guides (User, Administrator, Developer) Release BETA Meeting - Geneva, 1-2 March 2007
Distribution Web Application Improvements and changes for BETA Beta Release Deployment scenarios Integration of the WebApp with the DILIGENT portal More difficult maintenance for Eng and support from UoA Requires Integration Effort (depending on the technology used for the Portal) Solves the Access Control issue Static pages in the DILIGENT Portal Easier integration No Dynamicitiy of the Application (HEAD WA cannot be moved) Independent server (currently grids16.eng.it) Easier maintenance No integration required WA and Portal access control still independent Release BETA Meeting - Geneva, 1-2 March 2007