ci(buildkite): exclude files/folders that are not tested in Buildkite

[v1v]

What does this PR do?

Skip files that are not used in Buildkite

Why is it important?

Run faster builds and avoid waste of CI cycles.

I decided to support the whole .github folder since some other files, such as CODEOWNERS or .dependabot.yml, and the rest are not used by Buildkite.

The same for the docs, IIUC, that's not tested in BK itself but a BK docs pipeline owned by the docs team

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b0a5095

History

• 💚 Build #4718 succeeded 2df6bc5

cc @v1v

[mrodm]

One doubt here @v1v, in this repository, the elastic-package Buildkite pipeline is a required check status in Pull Requests to be able to merge it. The same configuration is applied in other repositories like integrations or package-spec (in their corresponding pipelines).

What would happen for those Pull Requests that do not trigger the given build?

IIUC, if this PR is merged, all the following PRs updating just those files should be merged bypassing branch protections. Is that the expected approach?

EDIT:
Could it be that the status check for that pipeline is set to "success" in those cases?
Checking the configuration, the set_commit_status is set to true, so maybe that helps here.

[v1v]

That's a good question. I created elastic/beats#42437 and it passed the GH check:

So the GH check should be the name of the BK pipeline rather than a subset of the steps.

Is that the case?

[mrodm]

That's a good question. I created elastic/beats#42437 and it passed the GH check:

So the GH check should be the name of the BK pipeline rather than a subset of the steps.

Is that the case?

Perfect! it marks the pipeline status as successful 👍 In our case, we just have one status check per pipeline, so that's good.

Thanks for checking this out!