From 400e9e72c7051de59a2f9eb22a304e9e7d901819 Mon Sep 17 00:00:00 2001 From: Martijn Laarman Date: Sun, 3 May 2026 21:37:55 +0200 Subject: [PATCH] Fix docs-build-pr not triggering on elastic/docs PRs The docs-build-pr pipeline has a branch filter in Buildkite that only allows master. All other repos in job 0 use always_trigger_branch:master so they always build against master and pass the filter. The standalone elastic/docs job (job 1) has no always_trigger_branch, so the pr-bot triggers against the PR's feature branch which the pipeline filter silently rejects. Previously builds appeared to work because the doc-preview GitHub Actions workflow posts a comment containing the text "run docs-build", which accidentally matched the old unanchored trigger_comment_regex. Tightening the regex with ^ and $ anchors (#3327) inadvertently removed that accidental trigger. Setting ignore_pipeline_branch_filters: true tells the Buildkite API to bypass the pipeline's branch filter, allowing build_on_commit and comment triggers to work as intended per the buildkite-pr-bot design. Co-Authored-By: Claude Sonnet 4.6 (1M context) --- .buildkite/pull-requests.org-wide.json | 1 + 1 file changed, 1 insertion(+) diff --git a/.buildkite/pull-requests.org-wide.json b/.buildkite/pull-requests.org-wide.json index fa7d2ddb737c..9c77344dcc22 100644 --- a/.buildkite/pull-requests.org-wide.json +++ b/.buildkite/pull-requests.org-wide.json @@ -91,6 +91,7 @@ "allowed_list": ["github-actions[bot]", "renovate[bot]", "mergify[bot]"], "build_on_commit": true, "build_on_comment": true, + "ignore_pipeline_branch_filters": true, "trigger_comment_regex": "^run docs-build ?(?rebuild)? ?(?warnlinkcheck)? ?(?skiplinkcheck)?\\s*?$", "always_trigger_comment_regex": "^buildkite test this ?(?rebuild)? ?(?warnlinkcheck)? ?(?skiplinkcheck)?\\s*?$", "skip_ci_labels": [