ci: add Buildkite PR analysis agentic workflow

[margaretjgu]

Summary

• Adds .github/workflows/buildkite-pr-analysis.md, a gh-aw agentic workflow that mirrors the pattern already in use in elasticsearch-specification (kibana-type-check-analysis)
• On each PR, it polls the elasticsearch-js-integration-tests Buildkite pipeline for the build matching the PR's head commit, fetches logs from failed jobs, and uses Claude to post a concise comment on the PR summarising failures by root cause (regression vs. flake)

[prodsecmachine]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

Buildkite Integration Test Analysis

Build: [elasticsearch-js-integration-tests #3855]((buildkite.com/redacted) — failing

⚠️ Limited analysis: The pre-step that fetches failed job logs did not produce a failed-jobs.txt file, and the Buildkite URL requires authentication that is unavailable in this workflow context. Detailed per-test failure output could not be retrieved.

What is known

Item	Detail
Build state	failing
PR	Adds .github/workflows/buildkite-pr-analysis.md — a new agentic CI workflow
Likely scope	This is a meta-PR introducing the workflow itself, so the failure may be a first-run bootstrapping issue or a configuration gap in the new workflow

Suggested next steps

1. Open the build directly → [Build #3855]((buildkite.com/redacted) and inspect which jobs failed.
2. Check whether failed-jobs.txt should have been written — if the pre-step that fetches Buildkite logs failed silently, that is itself a bug to fix in this PR.
3. Re-run the build to rule out a transient infrastructure failure, since no test-level evidence is available to distinguish regression from flake.
4. If the failure is in a job unrelated to the new workflow file (e.g. a standard integration test), compare against recent main builds to assess whether it pre-dates this PR.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• buildkite.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "buildkite.com"

See Network Configuration for more information.

Generated by Buildkite PR analysis for issue #3349 · ● 606.9K · ◷

[github-actions]

Buildkite Integration Test Results

Build: elasticsearch-js-integration-tests #3856 — ❌ failing

---

Analysis

The pre-step that fetches failed job logs did not produce a failed-jobs.txt file, so a detailed per-failure breakdown is not available for this run.

Suggested next steps:

1. Open the Buildkite build directly to inspect which jobs failed and review the raw logs.
2. Check whether the failure is in the workflow step that fetches Buildkite logs (i.e. the pre-step itself may have errored before writing output) — this PR adds the workflow, so a bootstrap/first-run issue is likely.
3. Re-run the build once the workflow is confirmed to be writing failed-jobs.txt correctly to get a full analysis on the next attempt.

Generated by Buildkite PR analysis for issue #3349 · ● 595.9K · ◷

[github-actions]

Integration Test Build Failure

The Buildkite integration test build for this PR is failing: Build #3857

Note: Detailed failure annotations and job logs were not available for automated analysis. Please check the Buildkite link above for the full failure details.

Suggested next steps:

1. Review the failing jobs in the Buildkite build linked above.
2. Check whether the failures are related to changes in this PR or are pre-existing infrastructure/flake issues.
3. If the failures appear transient (network timeouts, infrastructure errors), re-run the build to confirm.
4. If the failures are test regressions, investigate the specific test output in Buildkite and address accordingly.

Generated by Buildkite PR analysis for issue #3349 · ● 559.8K · ◷