Skip to content

bk: sparse checkout for loading bk pipelines#50662

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

bk: sparse checkout for loading bk pipelines#50662
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

Proposed commit message

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

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
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@v1v v1v self-assigned this May 13, 2026
@v1v v1v added backport-skip Skip notification from the automated backport with mergify skip-changelog labels May 13, 2026
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 13, 2026
@botelastic
Copy link
Copy Markdown

botelastic Bot commented May 13, 2026

This pull request doesn't have a Team:<team> label.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 13, 2026

🤖 GitHub comments

Just comment with:

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

@v1v v1v marked this pull request as ready for review May 14, 2026 15:15
@v1v v1v requested a review from a team as a code owner May 14, 2026 15:15
@v1v v1v mentioned this pull request May 14, 2026
Open
6 tasks
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 7539e557-278b-440b-8fdb-cfee4af17e2f

📥 Commits

Reviewing files that changed from the base of the PR and between 0e87a23 and 9b6f67a.

📒 Files selected for processing (1)
  • catalog-info.yaml
📝 Walkthrough

Walkthrough

This pull request updates catalog-info.yaml to add a sparse-checkout#v1.6.0 initial step plugin configuration to 24 buildkite pipeline resources. Each resource now limits its repository checkout to the .buildkite directory and .go-version file, with sparse state cleanup enabled. The configuration is applied consistently across heartbeat, deploy-k8s, beats variants, x-pack beats, and packaging/validation/scheduling pipelines.

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • 🛠️ Update Documentation

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Reviewers

No reviews

Assignees

@v1v v1v

Labels

backport-skip Skip notification from the automated backport with mergify needs_team Indicates that the issue/PR needs a Team:* label skip-changelog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@v1v