| 5 | | == Introduction == |
| 6 | | |
| 7 | | The purpose of this project is to create an infrastructure that is capable of implementing quality control jobs against the Bcfg2 code. |
| 8 | | |
| 9 | | == Proposed Stories for Project == |
| 10 | | |
| 11 | | * As a developer and VCS manager, I want to know my commits do not break the building of packages for debian. |
| 12 | | * As a developer and VCS manager, I want to know my commits do not break the building of packages for redhat. |
| 13 | | * As a developer and VCS manager, I want to know new commits do not break existing nose tests. |
| 14 | | |
| 15 | | == Rough Outline for Building Infrastructure == |
| 16 | | |
| 17 | | Some questions that need to be answered as we develop this infrastructure: |
| 18 | | |
| 19 | | * Do we want to use CI to publish builds? |
| 20 | | * What tests can we do on the jenkins machine and which are best [https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds distributed to slave build boxes]? |
| 21 | | * Does the [http://trac.mcs.anl.gov/projects/bcfg2/browser code repository] need to change to accommodate automatic builds? |
| 22 | | * Who gets communications about jobs? (e.g. irc, commiters, mergers, mailing list) |
| 23 | | |
| 24 | | === Phase 1 === |
| 25 | | * Set up a [http://jenkins-ci.org/ Jenkins] servers. |
| 26 | | * Set up jobs for building Bcfg2 |
| 27 | | * Set up jobs for running existing tests |
| 28 | | |
| 29 | | === Phase 2 === |
| 30 | | |
| 31 | | ??? |
| 32 | | |
| 33 | | == Glossary == |
| 34 | | |
| 35 | | * Jobs |
| 36 | | * Builds |
| | 5 | https://travis-ci.org/Bcfg2/bcfg2 |
