"QA in TYPO3 - CI in a community-driven os project"
summary
CI for TYPO3 shows concrete scale and choices: GitLab pipelines run roughly 60,000 pipelines and over 3.5 million jobs in recent years, delivering patch feedback in 5–6 minutes using four Hetzner machines (16 cores, 128 GB) with 20+ parallel jobs. The monorepo holds ~11,600 unit tests, ~7,500 functional tests that spin up full TYPO3 instances, nightly permutations catch dependency edge cases, Podman replaces Docker for security, and images are built for amd64 and ARM so failures reproduce locally.
AI-written summary · about
chapters (15)
- 0:00Introduction to QA in TYPO3
- 1:06Why quality assurance matters
- 4:39Open source CI challenges
- 6:05Project size and codebase facts
- 9:18CI testing scope and platforms
- 13:13Early and frequent testing strategy
- 17:09Patch testing and nightly tests
- 20:39Testing levels and tools
- 23:28History of test automation
- 26:21CI infrastructure evolution
- 28:05GitLab review and CI process
- 30:13Container images and hardware
- 34:27Open CI infrastructure sharing
- 35:52Security implications of CI setup
- 36:55Key learnings from TYPO3 QA
related talks
45mHighway to Continuous Integration
25mA song of DevOps and TYPO3 - Developing a platform to host TYPO3
01h 00mCI/CD, the Jobtech way
40mCode, Test, Deploy, Repeat
28mKeeping Developers Happy with a Fast CI
32mTools for Better Testing for Open Source Projects
35mMassively Continuous Integration: From 3 days to 30 minutes
38mWhat's Really to Blame?