Developer, Testing, Release and Continuous Integration Automation Miniconf 2015
This miniconf is all about improving the way we produce, collaborate, test and release software.
We want to cover tools and techniques to improve the way we work together to produce higher quality software:
- code review tools and techniques (e.g. gerrit)
- continuous integration tools (e.g. jenkins)
- CI techniques (e.g. gated trunk, zuul)
- testing tools and techniques (e.g. subunit, fuzz testing tools)
- release tools and techniques: daily builds, interacting with distributions, ensuring you test the software that you ship.
- applying CI in your workplace/project
- 10:40 Nick Coghlan - Beaker's Hardware Inventory System
- 11:10 Steve Kowalik - Testing the cloud in the cloud
- 11:35 Fraser Tweedale - The Best Test Data is Random Test Data
- 12:00 Sarah Kowalik & Jesse Reynolds - Developers, sysadmins, and everyone else: Why you should be using Serverspec
- 13:20 Matthew Treinish - Subunit2SQL: Tracking Individual Test Results in OpenStack's CI System
- 13:45 Raghavendra Prabhu - Corpus collapsum: Partition tolerance of Galera put to test
- 14:15 Sven Dowideit - Kickstart new developers using Docker
- 14:35 Joe Gordon - Large Scale Identification of Race Conditions (In OpenStack CI)
- 15:40 Anita Kuno - Gerrit & Gertty: A Daily Habit
- 16:10 Dr. Jason Cohen - Incorporating the Security Development Life Cycle and Static Code Analysis into our Everyday Development Lives: An Overview of Theory and Techniques.
- 16:35 Discussion / Q&A
Beaker's Hardware Inventory System
By Nick Coghlan
Ever wondered what it might take to track down and resolve a kernel bug that only affects one particular variant of one particular processor architecture from one particular vendor? Step one is going to be actually getting hold of a suitable machine, and for that, you'll need an inventory system that provides that level of detail.
Red Hat's Beaker integration and testing system provides such a service. This talk will describe the inventory gathering component of Beaker including the transition from using ""smolt"" to ""lshw"" for this component and how the Beaker team is able to use access to more esoteric hardware to enhance the capabilities of lshw.