[9.2] (backport #11612) ci(packaging): let's test the packaging pipeline on PRs too #11628
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This pull request introduces an early trigger for the Elastic Agent Package pipeline in the Buildkite CI process, it runs
the https://buildkite.com/elastic/elastic-agent-package with dry-run using the versions defined at
.package-versionWhy is it important?
aiming to catch integration issues earlier during pull request builds.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Only in the CI, now it triggers a new step if changes are made in the main pipeline or any other related files with the packaging.
In this case, it ran https://buildkite.com/elastic/elastic-agent-package/builds/8694
Related issues
Questions to ask yourself
This is an automatic backport of pull request #11612 done by [Mergify](https://mergify.com).