[ci] Allow triggering exhaustive tests from PRs depending on path #18202
Conversation
This file contains hidden or 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
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
This pull request does not have a backport label. Could you fix it @oakrizan? 🙏
|
oakrizan
changed the title
oakrizan
added
ci
backport-active-all
oakrizan
requested review from
v1v,
dliappis and
fr4nc1sc0-r4m0n
and removed request for
v1v
oakrizan
force-pushed
the
feature/trigger-exhaustive-tests-on-path
branch
from
27f9e6d to
eb8c8e4
Compare
v1v
reviewed
Sep 23, 2025
v1v
reviewed
Sep 24, 2025
|
💚 Build Succeeded
History
|
v1v
reviewed
Sep 25, 2025
Comment on lines
+41
to
+45
| "allowed_list": [ | ||
| "dependabot[bot]", | ||
| "mergify[bot]", | ||
| "github-actions[bot]" | ||
| ], |
There was a problem hiding this comment.
If we don't build on comment, should we remove this entry?
v1v
reviewed
Sep 25, 2025
Comment on lines
+53
to
+58
| "skip_ci_on_only_changed": [ | ||
| "^.github/", | ||
| "^docs/", | ||
| "^.mergify.yml$", | ||
| "^.pre-commit-config.yaml", | ||
| "\\.md$" |
There was a problem hiding this comment.
If we don't build on commit should we remove these entries?
v1v
reviewed
Sep 25, 2025
| "github-actions[bot]" | ||
| ], | ||
| "set_commit_status": true, | ||
| "build_on_commit": false, |
There was a problem hiding this comment.
I'm certainly confused with the description and this flag
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.
Release notes
rn:skip
What does this PR do?
Adds initial setup to trigger the exhaustive tests on specific paths that were changed.
Why is it important/What is the impact to the user?
Test the code that will rarely impact the standard PR test suite, but will exercise the acceptance tests.
Checklist
[ ] 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 (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
Add a path to
always_require_ci_on_changedin pull-request.json forlogstash-exhaustive-tests-pipeline, then apply changes in that directory, commit and push. That will trigger the exhaustive tests pipeline in Buildkite.