Issue Task Resolved

#110352Parallelize e2e-install database jobs in CI

Stefan Bürk 08/01/26, 13:46 updated 08/01/26, 16:20

Description

Problem

Both the pre-merge and the nightly “e2e install” jobs execute the installer
end-to-end tests for all four database backends (mariadb, mysql, postgres,
sqlite) sequentially within a single job. In the nightly pipeline this happens
twice, once for the “max” and once for the “min” dependency set.

Each backend rebuilds a full composer TYPO3 instance from scratch, including the
“vendor/bin/typo3 setup” run – the installer mutates state irreversibly, so the
instance cannot be reused across backends. The four serial installs therefore
sit on the critical path of one job and dominate its wall-clock.

Solution

Split each of these jobs into one job per database backend, mirroring the
existing functional test matrix: four pre-merge jobs and, for nightly, four
“max” plus four “min” jobs. The backends then run concurrently on separate
runners, cutting the wall-clock of that step roughly fourfold at unchanged
aggregate work.

Every job keeps its “retry: 2” whole-job retry, since an in-test retry can never
recover a tainted instance.

Reviews 2