Skip to content

[Skills] Add Buildkite logs skill#258587

Merged
CoenWarmer merged 7 commits intoelastic:mainfrom
CoenWarmer:add-skill-for-buildkite-log
Mar 23, 2026
Merged

[Skills] Add Buildkite logs skill#258587
CoenWarmer merged 7 commits intoelastic:mainfrom
CoenWarmer:add-skill-for-buildkite-log

Conversation

@CoenWarmer
Copy link
Copy Markdown
Contributor

@CoenWarmer CoenWarmer commented Mar 19, 2026

Summary

Adds a skill to help agents understand Buildkite logs for Kibana PRs.

Useful when investigating failing / flaky tests, but also helping it find examples of runtime behavior on the CI.

@CoenWarmer CoenWarmer requested a review from a team as a code owner March 19, 2026 16:08
@CoenWarmer CoenWarmer added backport:version Backport to applied version labels v9.1.0 v9.2.0 v9.3.0 9.4.0 release_note:skip Skip the PR/issue when compiling release notes labels Mar 19, 2026
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need to update the CODEOWNERS entry to add this file. I think our team can own this as it seems testing related.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sgtm!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added to code owners

@CoenWarmer CoenWarmer requested a review from csr March 20, 2026 10:05
@CoenWarmer CoenWarmer added v9.4.0 and removed 9.4.0 labels Mar 20, 2026
@CoenWarmer CoenWarmer enabled auto-merge (squash) March 20, 2026 11:22
fi
BK_AUTH="Authorization: Bearer $BUILDKITE_API_TOKEN"
ORG="elastic"
PIPELINE="kibana"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The kibana pipeline doesn't exist. We may want to use another example.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed with cffc0cf

/.agents/skills/scout-migrate-from-ftr/** @elastic/appex-qa
/.agents/skills/scout-ui-testing/** @elastic/appex-qa
/.agents/skills/enzyme-to-rtl/** @elastic/appex-qa
.agents/skills/buildkite-logs @elastic/appex-qa
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we please add a trailing / (it shouldn't technically be necessary, but is what I see the other paths use).

Copy link
Copy Markdown
Contributor Author

@CoenWarmer CoenWarmer Mar 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, was rushing and missed this. Addressed with cffc0cf

```

To get a build number from a Buildkite URL like
`https://buildkite.com/elastic/kibana/builds/123456`, extract `123456`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is just an example, but I'd use a "semi-working" example here:

Suggested change
`https://buildkite.com/elastic/kibana/builds/123456`, extract `123456`.
`https://buildkite.com/elastic/kibana-pull-request/builds/123456`, extract `123456`.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Addressed with cffc0cf


---

## Fetch latest build for a PR
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really cool!

Copy link
Copy Markdown
Member

@csr csr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I think this is a good and effective first iteration.

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #79 / Endpoint plugin @ess @serverless @skipInServerlessMKI When attempting to call an endpoint api "before all" hook in "@ess @serverless @skipInServerlessMKI When attempting to call an endpoint api"

Metrics [docs]

✅ unchanged

History

@CoenWarmer CoenWarmer merged commit 7ad870f into elastic:main Mar 23, 2026
15 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 9.1, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/23457728938

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
9.1 Backport failed because of merge conflicts
9.2 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.2:
- move kbn-client into its own package (#258963)
9.3 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.3:
- move kbn-client into its own package (#258963)

Manual backport

To create the backport manually run:

node scripts/backport --pr 258587

Questions ?

Please refer to the Backport tool documentation

kubasobon pushed a commit that referenced this pull request Mar 24, 2026
## Summary

Adds a skill to help agents understand Buildkite logs for Kibana PRs.

Useful when investigating failing / flaky tests.
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 25, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

jeramysoucy pushed a commit to jeramysoucy/kibana that referenced this pull request Mar 26, 2026
## Summary

Adds a skill to help agents understand Buildkite logs for Kibana PRs.

Useful when investigating failing / flaky tests.
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

1 similar comment
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

12 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 258587 locally
cc: @CoenWarmer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport missing Added to PRs automatically when the are determined to be missing a backport. backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes v9.1.0 v9.2.0 v9.3.0 v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants