Version 2 (modified by rcuza, 11 years ago) (diff) |
---|
Bcfg2 Continuous Integration
This document is a draft.
Introduction
The purpose of this project is to create an infrastructure that is capable of implementing quality control jobs against the Bcfg2 code.
Proposed Stories for Project
- As a developer and VCS manager, I want to know my commits do not break the building of packages for debian.
- As a developer and VCS manager, I want to know my commits do not break the building of packages for redhat.
- As a developer and VCS manager, I want to know new commits do not break existing nose tests.
Rough Outline for Building Infrastructure
Some questions that need to be answered as we develop this infrastructure:
- Do we want to use CI to publish builds?
- What tests can we do on the jenkins machine and which are best distributed to slave build boxes?
- Does the code repository need to change to accommodate automatic builds?
- Who gets communications about jobs? (e.g. irc, commiters, mergers, mailing list)
Phase 1
- Set up a Jenkins servers.
- Set up jobs for building Bcfg2
- Set up jobs for running existing tests
Phase 2
???
Glossary
- Jobs
- Builds