Hi folks as part of what I'm doing in GENIVI and AGL, I've undertaken to prepare a Statement of Work for public-facing continuous integration and automated test infrastructure. I've taken the liberty of starting a draft of this on the Baserock Wiki at [1] because ikiwiki is my weapon of choice in the wiki wars so far, and I am aware this topic is of interest to various Baserock constituents. Also, I know that we've experimented with various approaches and had success with some of the relevant technologies for Baserock itself. My hope is to get the implementation moving quickly, using available FOSS solutions as far as possible, and therefore I'll be happy to recommend Baserock tooling (eg Trove) if it clearly makes sense and can fit with established technology choices (eg Bitbake for builds). I'd very much appreciate feedback and comments here before I submit a second draft for consideration elsewhere. The text is below. I'll be happy to incorporate any comments received by reply here on the list or as private email. br Paul SoW: Continuous Integration and Automated Test ===================================== Background -------------- Various open source 'umbrella' projects including GENIVI, AGL and PRPL have a need to establish and maintain public-facing infrastructure for Continuous Integration and Automated Testing of their software architectures. This aims to document generalised requirements for CIAT in a 'Statement of Work' form, so that actual implementations can be planned and delivered. It is hoped that a workable solution can be found which satisfies requirements for all of these organisations, but it is expected that each may have further specific requirements, and may for its own reasons choose alternative approaches for some or all of the parts of this infrastructure to satisfy organisation-specific goals. The content here is offered to all of the mentioned organisations (and more widely) for consideration. It is recognised that maintaining a CIAT infrastructure can be of significant engineering value, but involves ongoing work and cost. Therefore collaboration on a generally useful approach can offer particular benefits both in terms reduced cost per project, and increased quality through (for example) cross-validation and re-use of tests. Scope -------- CIAT includes * collection of source code from upstreams including new versions as required on an ongoing basis * recipes and/or automated instructions for building the upstream components * recipes and/or automated instructions for installing the upstream components into an integrated 'distro' * Continuous Integration tooling which executes the recipes/instructions automatically, either * on user demand, or * triggered by changes to the instructions or components themselves * publication of the built/integrated artefacts which are output by the execution of the ci tooling * Automated Test tooling which executes sets of tests on deployed instances of the integrated software * publication of the results of the automated tests * demonstration of license compliance * machanism for formal code review prior to merging of changes, either * before build and test or * after build and test as candidate (preferred) Requirements ---------------- * all of the CIAT software tooling must be FOSS * any custom work to make the solution fit specific use-cases for GENIVI, AGL, PRPL must be FOSS * where possible the solution should align with the upstream developers for its components. * instructions for creation and setup of a working instance of CIAT infrastructure must be provided * minimal manual maintenance - the system should be mostly automated: * minimal effort for license compliance (eg scripted license checking, publish applicable source for all artefacts) * developer/integrator engineers can trigger build/test using git push. * CIAT must support * several automated test frameworks (eg fitnesse, phoronix, LTSI Test Project) * testing scenarios on multiple architectures (eg ARMv7, x86_64) for both virtual machines (eg QEMU) and actual hardware [1] http://wiki.baserock.org/ciat/