Skip to content

add parameters to pr bot org wide config #2801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 24, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .buildkite/pull-requests.org-wide.json
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,16 @@
],
"build_on_commit": true,
"build_on_comment": true,
"trigger_comment_regex": "^(?:(?:buildkite\\W+)?(?:build|test)\\W+(?:this|it))",
"always_trigger_comment_regex": "^(?:(?:buildkite\\W+)?(?:build|test)\\W+(?:this|it))",
"trigger_comment_regex": "run docs-build ?(?<rebuild_opt>rebuild)? ?(?<warn_opt>warnlinkcheck)? ?(?<skip_opt>skiplinkcheck)?",
"always_trigger_comment_regex": "run docs-build ?(?<rebuild_opt>rebuild)? ?(?<warn_opt>warnlinkcheck)? ?(?<skip_opt>skiplinkcheck)?",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't tested these regular expressions but I'll assume they work.

@bmorelli25 @jrodewig It's probably good to note for when the documentation is updated that the options need to be in order. I don't know how the new Buildkite script handles them; in Jenkins it just searched for the "rebuild"/"skiplinkcheck" text anywhere in the comment body. But in terms of a trigger phrase I think they'll need to be in this order.

"skip_ci_labels": [
"skip-ci"
],
"skip_ci_on_only_changed": [
"\\.md$"
".*"
],
"always_require_ci_on_changed": [
"docs\\.*"
],
"repositories": [
"elastic/docs",
Expand Down