Download - Full Automation for Continuous Validation
#
Joshua GraffDevelopment Operations Manager
Full Automation for Continuous Validation
#
• Who am I?
• What is Xilinx?
The Who
#
A Story of Growth
1/1/02 1/1/03 1/1/04 1/1/05 1/1/06 1/1/07 1/1/08 1/1/09 1/1/100
50100150200250300350400
Total Active Developers
#
The Beginning
P4
C1
C2
C3
#
Early Growth
1/1/02 1/1/03 1/1/04 1/1/05 1/1/06 1/1/07 1/1/08 1/1/09 1/1/100
50100150200250300350400
Total Active Developers
#
Continuous Revolution
P4
C1
C2
C3
#
Rapid Expansion
1/1/02 1/1/03 1/1/04 1/1/05 1/1/06 1/1/07 1/1/08 1/1/09 1/1/100
50100150200250300350400
Total Active Developers
#
• Majority of failures on one platform
• High rate of failures due to files missing from a CL
• Conclusion
Investigation
#
• Build multiple platforms
• Perform aliveness smoke tests
• Check workspace integrity
Enter “pre-commit”
#
New Workflow
P4
C1
C2
C3
pre-commit
pre-commit
pre-commit
#
Final Frontier
1/1/02 1/1/03 1/1/04 1/1/05 1/1/06 1/1/07 1/1/08 1/1/09 1/1/100
50100150200250300350400
Total Active Developers
#
• Workspace integrity is hard
• Dependent changes
• Remote site and user support difficulties
• No true enforcement
Problems
#
• Control of Workspaces
• Isolate changes
• Leverage core infrastructure
• Be enforceable
Solution
#
Enter “The Wall”
P4Wallwall-submit
wall-submit
wall-submit
#
How does it work?
+ P4
Workers
wall-submit Wall(Foreman)
Workspaces
S1
#
Interaction
#
Interaction
#
• Fire and Forget
• Fire and do something else
• Remote and alternative development
• Intelligent validation
New Paradigm
#
• Building and supporting critical infrastructure
• The ever growing desire to validate more
• Resources
• Guaranteed change delivery
Challenges
#
• Cloning
• Reprioritization
• More intelligent validation
The Future
#
Today
1/1/02 1/1/03 1/1/04 1/1/05 1/1/06 1/1/07 1/1/08 1/1/09 1/1/100
50100150200250300350400
Total Active Developers
#
Final Thoughts• Ideas
