[bric3]

What Does This Do

Apply builder image fingerprints to seven projects whose tests and nested smoke builds consume image tools or native libraries. Supply ciBuilderImage through one global ORG_GRADLE_PROJECT_ciBuilderImage variable derived from the existing builder repository and version prefix.

Motivation

Changing the configured builder version should invalidate affected test and native-build outputs alongside the existing JVM fingerprints.

Additional Notes

Confirmed consumers of builder image contents:

Image contents	Confirmed consumers
System ls	ContainerInfoTest invokes ls -id.
echo, cat, sleep, tail	PortableCommandTest; ShellCommandExecutorTest invokes the first three.
Native runtime / libc	ErpcTlsTest uses JNA native memory; CWS loads libc through ErpcTls and Erpc.
libc variant	ddprof controller tests load the bundled native profiler selected for the current libc variant.
GraalVM and native tools	Spring and Quarkus smoke producers compile native executables in nested Gradle builds.

Native builds already fingerprint the GraalVM release contents through #13083. This PR adds the builder identity to test and native producer inputs. Compiler tasks keep Gradle's toolchain inputs.

• Relates to Track smoke artifacts and configurable build inputs #13083
• Stacked on Track CI builder images in selected task inputs #13084.

The value currently identifies the configured image version. Republishing an image under the same tag leaves it unchanged. CI can later supply the image content hash through the same property.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.47% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: fc1a646 | Docs | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.99 s	13.90 s	[-0.1%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	13.03 s	[-1.6%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	17.74 s	17.47 s	[+0.6%; +2.4%] (maybe worse)
startup:petclinic:iast:Agent	17.43 s	17.66 s	[-2.3%; -0.3%] (maybe better)
startup:petclinic:profiling:Agent	17.06 s	17.36 s	[-2.7%; -0.8%] (maybe better)
startup:petclinic:sca:Agent	17.62 s	17.48 s	[-0.0%; +1.7%] (no difference)
startup:petclinic:tracing:Agent	16.60 s	16.81 s	[-2.2%; -0.3%] (maybe better)

Commit: fc1a6466 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-28T13:32:27.651641Z	1341e44	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-28T13:33:19.905059Z	1341e44	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-prod-us1-4]

More details

Configured builder-version changes enter the selected task fingerprints, including both native smoke builds. Republishing the same image tag remains outside this cache-invalidation scheme, as documented.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 1341e44}

[bric3]

note: This is related to the task of building the build-image in this pipeline.

[sarahchen6]

Nice