The Qt Continuous Integration System
summary
A Continuous Integration system for Qt at Nokia compiles and runs the automated test suite against a baseline through a quality gate, uses staging branches (currently seven) to avoid blocking other developers, and reports successes or failures with links to logs. It runs on Pulse CI with ~200 agent machines and ~250 VMs on VMware ESX, uses Perl-heavy test scripts and Puppet for orchestration, targets ~200 core developers, aims for ~2.5 hour full-test runs per platform, and handles flaky tests via blacklists and manual review.
AI-written summary · about
chapters (8)
- 0:00Introduction to Qt CI
- 1:11Why Qt needs CI
- 8:16How Qt CI works
- 15:20Staging branches explained
- 25:02Test reports and challenges
- 35:25Social and technical challenges
- 39:37Future improvements
- 49:57Q&A session
related talks
45mHighway to Continuous Integration
28mIntel’s Middle Out Journey to DevOps
32mBuilding Continuous Integration and Feedback
53mContinuous Integration and Testing of a Yocto Project Based Automotive Head Unit
45mRunning Tests in Continuous Integration
30mQA in DevOps: Transformation thru Automation via Jenkins
45mCI Excellence With Test Automation Engineers
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned