1 / 8

NWO Build/Test system Framework

NWO Build/Test system Framework. - NMI Team. Snapshot. Overview Motivations Framework Component Glue Summary. Overview. Need for generic framework for building and testing components. Framework – Set of scripts that control/handle user scripts for building/testing their components.

wilbur
Download Presentation

NWO Build/Test system Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NWO Build/Test system Framework - NMI Team

  2. Snapshot • Overview • Motivations • Framework • Component Glue • Summary parag@cs.wisc.edu

  3. Overview • Need for generic framework for building and testing components. • Framework – Set of scripts that control/handle user scripts for building/testing their components. • Glue – Set of scripts written by the user to actually build/test the component. • Use DAGs to perform the task. parag@cs.wisc.edu

  4. Motivations Desired features • Easy of use. • Easy of adding new components without modifying the framework code. • Easy of adding new platforms without modifying the framework code. • Building multiple components at the same time if they are independent and follow the dependencies when required. • Log the build/test related information in the database. Future Enhancements • Web interface for component builders to build/test over the web. parag@cs.wisc.edu

  5. Framework • Building a product can be split into several tasks. Few are as follows … • Fetching the sources • Fetching the glue • Creating the source tarball • Compiling the source to get the binaries • Packaging the binaries in the desired manner. • Provide the required flexibility to the user to perform these tasks in the required manner. parag@cs.wisc.edu

  6. Framework … • Error and output reporting for each user and framework task. • Means for specifying the dependencies. • Tasks can be translated as nodes of a DAG. Each node is either dependent on some other node to complete or can be executed in parallel • Provide good interface to the glue scripts so user has the information about the progress of his/her tasks. • Independent of the glue or platform. parag@cs.wisc.edu

  7. Component Glue • Set of scripts written by the user to build/test the component • Scripts should be executed in a specific order. Example … • Fetching the sources • Fetching the glue • Creating the source tarball • Compiling the source to get the binaries • Packaging the binaries in the desired manner. • User writes a description file (very close to condor’s JDF) which contains the description of various tasks and the respective scripts to be invoked as a part of the build/test. This file acts as an input to the framework. • For detailed division of glue scripts http://www.cs.wisc.edu/condor/nmi/ parag@cs.wisc.edu

  8. Summary • An attempt to develop a framework that could be used to build and test components which is – • independent of the component • independent of the platform • good at logging the require information • handling complex tasks by splitting them into smaller sub tasks. parag@cs.wisc.edu

More Related