ci: reuse system-tests runner image - #4144
Open
bm1549 wants to merge 4 commits into
Open
Conversation
2 tasks
|
bwoebi
reviewed
Aug 27, 2026
bm1549
marked this pull request as ready for review
August 27, 2026 13:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
System-test jobs currently spend about 4m18s on recursive submodules and about 5 minutes installing Docker and Python tooling. This moves them to the upstream system-tests runner image, disables dd-trace-php submodules for these jobs, reuses the image virtualenv, and builds only the PHP weblog.
Each pipeline resolves
system-tests/mainonce inprepare codeand passes that exact SHA to every system-test job through a dotenv artifact. This keeps upstream source drift between pipelines without letting parallel jobs within one pipeline use different revisions.The runner stays content-addressed at
ci-runner:75a57a4b6391. Each job performs an exact shallow checkout, then runs the upstreambuild_ci_image.py --check-onlycheck before fetching Docker Hub or Datadog credentials. A change to the upstream runner Dockerfile orrequirements.txtfails early until this repository advances the image tag. Parent YAML defaults are moved into the generated child pipeline so the system-test override cannot be outranked by trigger variables.Expected impact: about 9m18s less wall time per executing job, roughly 2h38m of executor time across 17 routine expansions, or 6h31m when all 42 expansions run. Shallow-checkout savings are not included.
Tested with:
system-tests/maincheckout and source/image hash matchgit diff --checkReviewer checklist