Git structure for the Config Management SIG
We work under the centos-sig-configmanagement github organization.
Proposed CI flow
- One repository = one RPM
1. A public member of the github organisation opens a pull request
- A Scratch build is made on CBS
- Jenkins runs acceptance tests on that scratch build
- We send feedback to github
2. A github user opens a pull request
- We wait until a SIG member adds a comment [test] to the pull request
- A Scratch build is made on CBS
- Jenkins runs acceptance tests on that scratch build
- We send feedback to github
3. A commit is pushed to the repository
- A testing build is made on CBS
- Jenkins runs acceptance tests on that scratch build
- We send feedback to github
4. A tag is pushed to the repository
- A release build is made on CBS
- Jenkins runs acceptance tests on that tag build
- We send artifact to github releases
5. Tools
This is inspired by the foreman way of doing things.
We could reuse their tool https://github.com/theforeman/prprocessor
As the foreman does the sams thing without requiring to sign a CLA, we should not need that neither.