Describe QaWiki/CI/JJB here.
things we need to work out :
- namespace enforcement
- slave the jobs are going to run on == should be same as sig name and enforced.
- Keep reverse-track of jobs so we know which ones should be deleted (if a project removes its jobs)
- Allowing for workflows other than the ./run.sh workflow
- Letting "advanced" users specify their job steps
We have an index at https://github.com/CentOS/ci-index : <add notes on howto use it>
1.) Create a publicly available git repo for your test suite 2.) Submit a pull request to ci-index/project-index.yaml, adding your git url as a list item under the appropriate project heading 3.) A CI project member will merge your request 4.) Notice your new jobs in the jenkins interface