Make index tasks cacheable and improve input fingerprinting

[bric3]

What Does This Do

This PR makes the instrumentation index and agentJarIndex build tasks cacheable. Additionally, it improves how Gradle fingerprints task inputs for consistency and better cache normalization.

Motivation

Enabling task caching improves build performance by reusing outputs from previous executions. Adjusting input fingerprint normalization ensures accurate task caching behavior under different build environments.

Note

JavaExec is disabled for caching by default because Gradle needs task-specific input/output information. These index generators are deterministic for the same inputs, so declaring the missing metadata and enabling TaskOutputs.cacheIf lets Gradle restore their generated index files from the build cache instead of rerunning them.

Additional Notes

• The instrumentation index task no longer declares redundant input for the class path, as it is already specified in the JavaExec specification.
• The agentJarIndex task now uses PathSensitivity.RELATIVE for the expanded file tree.
  for input fingerprinting, focusing on relevant files below specific directories and improving CI build behavior.

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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f46f26b0f9

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that 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	14.00 s	13.97 s	[-0.4%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	12.94 s	13.01 s	[-1.3%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	16.70 s	16.78 s	[-1.6%; +0.6%] (no difference)
startup:petclinic:iast:Agent	16.86 s	16.98 s	[-1.6%; +0.2%] (no difference)
startup:petclinic:profiling:Agent	16.59 s	16.49 s	[-0.3%; +1.5%] (no difference)
startup:petclinic:sca:Agent	16.84 s	16.70 s	[-0.0%; +1.7%] (no difference)
startup:petclinic:tracing:Agent	16.06 s	16.16 s	[-1.6%; +0.3%] (no difference)

Commit: f46f26b0 · 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.