FIFA Gameplay Automated Testing with Jenkins
summary
Jenkins replaces one-machine bash scripts to run pre‑flight tests for FIFA, integrating via a Python interface with existing build tools and handling 10–20 GB builds by storing archives on each build machine and copying only a small descriptor to the master. The pipeline uses parallel build and test phases with the Build Flow DSL, evaluates ~500 changes (vs 200 previously) and finds ~10 problematic performance/stability changes; an integration job increases from 1/week to 10–20 per day on the build farm with automated reporting.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:30Improving Pre-Flight Testing with Jenkins
- 0:53FIFA Gameplay Pre-Flight Testing
- 1:42Limitations of Original System
- 2:13Why Jenkins?
- 2:44Moving to Jenkins
- 2:57Build Archiving - Typical Pattern
- 3:21Build Archiving . Challenges
- 3:46Build Archiving - Solution
- 4:41Build Pipelines - Design
- 5:15Build Pipelines - Implementation
- 8:33Project Outcomes
- 9:44Next Steps
related talks
10mFIFA Gameplay Automated Testing with Jenkins
36mFast Feedback: Jenkins+Functional & Non-Functional Mobile App Testing...
40mThe Butler Did It: Putting Jenkins To Work For You
40mAutomated Testing at Scale in Sea of Thieves
42mZero to Jenkins: Automatic builds + deploys
40mThe Secret to Scaling Performance Test Automation with Jenkins and JMeter
30mQA in DevOps: Transformation thru Automation via Jenkins
28mThe Butler and the Snake - Continuous Integration for Python
