|
|
Mesa's CI is composed of the following components:
|
|
|
|
|
|
* CI Master running jenkins and several services, and providing a common result directory for the system via nfs and rsyncd. [[jenkins master setup]]
|
|
|
|
|
|
* CI slaves which build software execute tests [[jenkins tester setup]]
|
|
|
|
|
|
* Compilation/test projects automated in python, supporting a common invocation interface. [[project description]]
|
|
|
|
|
|
* Build specification document, which configures dependencies between projects and git sources for projects. [[build spec]]
|
|
|
|
|
|
* Python modules shared by the projects implementing common functionality [[build_support]]
|
|
|
|
|
|
* A single parameterized jenkins job which builds any project, calling the common invocation interface. [[Leeroy]]
|
|
|
|
|
|
* Several top-level jenkins jobs which schedule sequences of project builds as required by dependencies. Results from all projects are collated for display in Jenkins UI and/or mailed to developers. [[schedulers]]
|
|
|
* Several top-level jenkins jobs which schedule sequences of project builds. Results from all projects are collated for display in Jenkins UI and/or mailed to developers. [[schedulers]]
|
|
|
* CI Master running jenkins and several services, and providing a common result directory for the system via nfs and rsyncd. [[jenkins master setup]]
|
|
|
* CI slaves which build software execute tests [[jenkins tester setup]]
|
|
|
|
|
|
Mesa CI has a consistent approach to managing test results and regressions: [[tracking test status]]
|
|
|
|
... | ... | |