When in a traditional software project, multiple components are to be integrated into a single working product, things nearly always go wrong. Continuous Integration is an approach to avoid this problem entirely, by automatically building and integrating all components whenever a developer makes a change. This way, large amount of design documentation and review sessions can be avoided, freeing up more time for actually making working software.

To do Continuous Integration right, a team must think about their group process, about how to use source control effectively, about the design of their components, and about how to do (automated) testing. In this talk, Egbert Teeselink, a GEWIS alumnus, will discuss how we do Continuous Integration at Sioux Embedded Systems, how we have learned and benefited from it, what we think we could do better, and how you can start doing Continuous Integration as well.