[bric3]

What Does This Do

Track the built smoke application and additional files as test inputs. In particular, a more precise version tracking, using the release file.

This adds an inputs { ... } hook to the smoke-test DSL. Each application can register named input providers through the regular Gradle's TaskInputs API. The Spring and Quarkus native applications use it to track their GraalVM release metadata.

Motivation

Smoke tests received application paths through JVM arguments, but the files were absent from their declared inputs! This didn't properly track the application and could allow build-cache reuse of a changed smoke test app.

Moreover application configurations also need to declare the external tools that affect their nested builds.

Additional Notes

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-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.46% (-0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4f1ca88 | 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.94 s	[-0.5%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	13.01 s	[-1.4%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.17 s	17.09 s	[-0.3%; +1.2%] (no difference)
startup:petclinic:iast:Agent	16.29 s	17.08 s	[-8.9%; -0.4%] (maybe better)
startup:petclinic:profiling:Agent	16.91 s	17.01 s	[-1.8%; +0.7%] (no difference)
startup:petclinic:sca:Agent	17.10 s	16.98 s	[-0.1%; +1.5%] (no difference)
startup:petclinic:tracing:Agent	16.29 s	16.11 s	[+0.2%; +2.1%] (maybe worse)

Commit: 4f1ca88d · 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-28T12:15:06.710217Z	a4b628d	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-28T12:15:23.025316Z	a4b628d	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-datadog-prod-us1]

More details

No reportable defect was identified in the artifact dependency wiring or lazy GraalVM metadata inputs. Confidence is limited to source inspection.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit a4b628d}

[sarahchen6]

Nice

[AlexeyKuznetsov-DD]

LGTM. left minor comment