1. C/C++ Build tools & Testbed
Jérémy Nguyen-Xuan (BE/CO/DO)

2. Build tools Currently, CommonBuild is used for Java development
C/C++ projects use make and /acc/local/
Move away from CommonBuild, Maven is a good candidate
Opportunity to unify the builds tools

3. Maven Maven NAR – Existing plugin for C/C++
Modified and extended Maven NAR to our needs with a solution based on Makefiles

4. Workflow Compilation phase Packaging phase Installation phase
Makefiles
Maven NAR
Maven NAR
Source code
Dependencies
Binaries
NAR package
Binary repository
Maven NAR
Resolve dependencies
Maven NAR
Dependency resolution phase

5. Usage
CMW – All products mavenized, used mainly for the Testbed deployment
Fesa3 – 50% of the projects converted, used for immediate feedbacks when check-in code
Timing – Prototyping for new timing system

6. Testbed Vision Reminder
Goals:
Ensure control system updates will not affect operations
Avoid late discovery of defects, bottlenecks and anomalies
Why?
Avoids costly mistakes
Provide more reliable products and services
Focus on development, not bug fixing for operation
Niall TC may 2009

7. Testbed Vision Reminder
How?
Test the Controls Core Components together
Certify that they work together before deployment
Become part of the standard Controls Workflow
Automate: lower testing effort and time
Scope:
Limited to Control System integration testing
Controls Core Components “release candidates” only
Not “for rent” to individual projects or teams
Niall TC may 2009

8. CO Testbed Hardware in place
TIMING
FEC03
SERVER06
SERVER07
FEC01
FEC02
Front Ends for Equipment
2 servers for applications
Timing for synchronization
FEC05
FEC04
Niall TC may 2009

9. The Testbed
Aims to improve quality through testing, for core controls components
Covered tests: functional, system, regression, backward compatibility
The tests are run automatically
Staging approach
Development
Release Candidate
Release

10. Testbed structure
Fesa3

11. Deployment in Testbed
Automatic build based on Bamboo

12. So far… Found several bugs and inconsistencies
Used for development (Fesa3, logging system, RBAC)
Test platforms (SLC6, Java7, 64-bit)
Testbed had to run intensively for 4 hours in order to expose a bug

13. Future plans Add stress tests Integrate more components
Enhanced tests to cover more scenarios
Make the Testbed a mandatory step in the build/release workflow

14. Conclusion
Testbed is expanding well and needs constant work
Maven, still in experimental state