bk: run faster builds

[v1v]

Proposed commit message

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

Using the spare checkout for the .buildkite folder and the .go-version file

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• see [CI] Use sparse checkout in pipeline upload kibana#265568
• Use sparse checkout for steps where we only upload buildkite pipelines elastic-agent#12082

Screenshots

[mrodm]

Adding this plugin looks really interesting!
Thanks!

Maybe it could be added to some other steps in the pipeline.

[mrodm]

Just to double check, is this plugin just used in the initial "Upload pipeline" step ?

I've triggered a Buildkite build to test this: https://buildkite.com/elastic/integrations/builds/42865

But I guess this is just applied once this PR is merged, so that build did not test anything does 😅

[v1v]

is this plugin just used in the initial "Upload pipeline" step ?

Yes, I've tested it already at https://buildkite.com/elastic/integrations/builds/42859 since I applied the changes manually

But I guess this is just applied once this PR is merged, so that build did not test anything does

correct

[mrodm]

Comparing with this other build: https://buildkite.com/elastic/integrations/builds/42832 1m7s vs 5s

This is a really good improvement, thanks!

[mrodm]

Thanks!!

[mrodm]

@v1v Just testing to create a Pull Request adding this plugin into more steps and pipelines , it looks like it could cause issues for those Pull Requests created with branches that start with the merge commit of this PR.

Errors seen:

HEAD is now at d57619a bk: run faster builds (#19006)
Current branch: HEAD
Switched to a new branch 'pr_merge_19015'
New branch created: pr_merge_19015
fatal: refusing to merge unrelated histories
Merge failed: 128
fatal: There is no merge to abort (MERGE_HEAD missing).

Post-checkout hook in this repository merges main branch with the PR branch to ensure that testing also contains the latest changes from main (similar to what Jenkins did here in the past).

I tried to use --allow-unrelated-histories parameter in the merge, but it also failed:

git merge --no-edit --allow-unrelated-histories "${BUILDKITE_COMMIT}"

I did two tests:

• A PR updating files under .buildkite/: [CI] Add sparse-checkout plugin to remaining pipelines and pipeline steps #19014
• A PR updating files for a package packages/nginx [CI] Test change in #19006 #19015

Context:

• Command failing in the post-checkout hook:
  

  integrations/.buildkite/hooks/post-checkout

  Lines 47 to 52 in d57619a

  	git merge --no-edit "${BUILDKITE_COMMIT}" || {
  	local merge_result=$?
  	echo "Merge failed: ${merge_result}"
  	git merge --abort
  	exit ${merge_result}
  	}

• [buildkite] Add new Buildkite pipelines to test packages with Serverless #8072
• [CI] Use the same commit from target branch for all steps in post-checkout hook #10397

I think this PR should be reverted to check how to apply this change taking into account this.