Fix report collection for build tooling projects

[AlexeyKuznetsov-DD]

What Does This Do

Collect reports from buildSrc and build-logic as well as workspace, using the actual project directory for copy, move, and delete operations. Enable nullglob so unmatched report roots are skipped.

Motivation

Build tooling reports outside workspace were omitted. Match the project roots used by the JUnit result collector while preserving the existing report layout for workspace projects.

Additional Notes

Validation: Bash syntax check; fixture checks covering copy, move, and delete across all three roots (9 combinations), plus an empty-root case. The extracted script is byte-for-byte identical to the source branch version.

With absent crash files, move mode prints harmless mv usage messages because unmatched globs disappear; commands retain the existing || true handling.

CI artifact before this fix:

CI artifact after this fix:

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-3]

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

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b429f75 | 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.91 s	13.93 s	[-0.8%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	12.90 s	[-0.3%; +0.8%] (no difference)
startup:petclinic:appsec:Agent	17.10 s	17.02 s	[-0.4%; +1.3%] (no difference)
startup:petclinic:iast:Agent	16.88 s	16.97 s	[-1.3%; +0.2%] (no difference)
startup:petclinic:profiling:Agent	16.48 s	16.81 s	[-3.0%; -1.0%] (significantly better)
startup:petclinic:sca:Agent	17.03 s	16.90 s	[-0.2%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	16.02 s	16.11 s	[-1.6%; +0.4%] (no difference)

Commit: b429f750 · 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-09T14:55:32.717105Z	b429f75	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-09T14:57:21.700377Z	b429f75	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-3]

More details

The report-root patterns match the JUnit collector, and workspace projects retain their existing archive destinations while build-tooling reports use their actual project paths.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit b429f75}

[bric3]

Nice improvement

[AlexeyKuznetsov-DD]

/merge -f --reason "No need to run MQ, validated in PR"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-09 16:16:41 UTC ℹ️ Start processing command /merge -f --reason "No need to run MQ, validated in PR"

---

2026-10-09 16:16:45 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-10-09 16:16:56 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: No need to run MQ, validated in PR