Skip to content

bk: sparse checkout for loading bk pipelines#19112

Draft
v1v wants to merge 1 commit into
elastic:mainfrom
v1v:feature/run-faster-builds
Draft

bk: sparse checkout for loading bk pipelines#19112
v1v wants to merge 1 commit into
elastic:mainfrom
v1v:feature/run-faster-builds

Conversation

@v1v
Copy link
Copy Markdown
Member

@v1v v1v commented May 13, 2026

see elastic/kibana#265568

Release notes

[rn:skip]

What does this PR do?

Check out faster when running the loading bk pipeline defined in the catalog-info

Why is it important/What is the impact to the user?

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

see elastic/kibana#265568
elastic/elastic-agent#12082

Use cases

Screenshots

Logs

@github-actions
Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 13, 2026

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant