Skip to content

Commit 838300a

Browse files
Mpdreamzclaude
andauthored
Fix docs-build-pr not triggering on elastic/docs PRs (#3332)
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) <noreply@anthropic.com>
1 parent f3bb9ad commit 838300a

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

.buildkite/pull-requests.org-wide.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@
9191
"allowed_list": ["github-actions[bot]", "renovate[bot]", "mergify[bot]"],
9292
"build_on_commit": true,
9393
"build_on_comment": true,
94+
"ignore_pipeline_branch_filters": true,
9495
"trigger_comment_regex": "^run docs-build ?(?<rebuild_opt>rebuild)? ?(?<warn_opt>warnlinkcheck)? ?(?<skip_opt>skiplinkcheck)?\\s*?$",
9596
"always_trigger_comment_regex": "^buildkite test this ?(?<rebuild_opt>rebuild)? ?(?<warn_opt>warnlinkcheck)? ?(?<skip_opt>skiplinkcheck)?\\s*?$",
9697
"skip_ci_labels": [

0 commit comments

Comments
 (0)