FIFA Gameplay Automated Testing with Jenkins
summary
Jenkins CI plus a Python interface integrates the existing build system, runs builds in parallel across a dedicated build farm, and automates reporting and build-graph visualization. Each build is 10–20 GB so the system keeps per-machine archives and only posts a small property file to the master, letting test nodes copy directly between machines. Pipelines use the Build Flow/Flow DSL to schedule parallel build and test closures and serialize results to JSON. Throughput rises: FIFA moves from 200 to 500 changes evaluated, finds ~10 problematic changes, and raises integrations from one per week to 10–20 per day.
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
34mUsing Test Automation for Continuous Integration, Delivery and Quality
40mAutomated Testing at Scale in Sea of Thieves
44mTaking CI and automated testing seriously
35mMassively Continuous Integration: From 3 days to 30 minutes
36mFast Feedback: Jenkins+Functional & Non-Functional Mobile App Testing...
32mBuilding Continuous Integration and Feedback
45mHow to Build a Performance Testing Pipeline from Scratch