Backport PR #15738 to 8.11: Run BK exhaustive pipeline when code is pushed #15771
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit enables running the exhaustive tests Buildkite pipeline (i.e. the equivalent to the `main` Jenkins tests) ; the trigger is code events, i.e. direct pushes, merge commits and creation of new branches. CI is skipped if changes are only related to files under `docs/`.
dliappis
changed the title
dliappis
changed the title
|
💚 Build Succeeded
cc @dliappis |
andsel
reviewed
Jan 10, 2024
There was a problem hiding this comment.
Why in PR #15770 there is a change to the catalog-info.yaml which is not present here?
@andsel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport PR #15738 to 8.11 branch, original message:
Release notes
[rn:skip]
What does this PR do?
As we are close to sunsetting Jenkins by completing the exhaustive tests Buildkite pipeline, it makes sense to start already running the existing phases (testing and compatibility).
This commit defines the trigger to be code events, i.e. direct pushes and merge commits, similar to what we currently have in Jenkins.
Why is it important/What is the impact to the user?
It allows us to gradually remove the corresponding phases from Jenkins to reduce CI duplication.
This will be especially useful when merging #15696 as the change is incompatible with Jenkins.
How to test this PR locally
An example build triggered manually can be found in https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/49#_
Unfortunately Windows tests will fail due to #15562
Related issues