User login
RSS Feed
Print this page
E-mail this page
Contact usETICS 2 (eInfrastructure for Testing, Integration and Configuration of Software)
The ETICS 2 project, the ETICS project's 2nd phase, is co-funded by the EU 7FP "e-Infrastructure - Capacity Programme". It provides a service to help software developers, managers and users to better manage complexity and improve the quality of their software. Using cutting edge Grid software and best practices, the ETICS service allows users to fully automate the way their software is built and tested. In other words, ETICS provides software professionals with an "out-of-the-box" build and test system, powered with a build and test product repository.
ETICS is multi-platform and open source. The client is designed to be simple to install. Results from daily, nightly and continuous builds and tests can be monitored via the web. Users can also browse and edit project data via a secured web application.
The collaboration with ETICS mainly concerns the technological area:
Technology
D4Science uses ETICS services as its build and integration platform. The current ETICS system is the result of two years of continuous refinement, where the collaboration with the DILIGENT (the predecessor of the D4Science project) team was a continuous source of feedback. D4Science has now fully standardized its software engineering process on it.
The D4Science integration and testing activity relies on the ETICS system for most of its tasks. This collaboration involves the different teams working in the preparation of the gCube releases. In particular:
- Developers rely on ETICS to execute local and remote builds of the component they are developing. ETICS is also useful for developers to share among them the different gCube components.
- The Build team exploits the ETICS system in the integration of the different software components provided by developers and builds a common gCube release. ETICS allows the execution of local and remote builds and the definition of different types of builds (continuous builds, integration builds, etc) by creating different configurations for the same component.
- The testing team uses ETICS for the execution of deployment tests and static code analyzers. The local or remote execution of these tests using ETICS facilitates and automatises the tasks of D4Science testers.
D4Science participated to the ETICS session in EGEE'08 (September 2008) by providing feedback about D4Science usage of the system. In particular, the current usage of ETICS for building and testing gCube and gCore was explained. Possible future improvements in ETICS were presented and discussed with the ETICS team.
- Login to post comments
