Fix invalid JSON escape \s in Buildkite trigger comment regexes#3330
Merged
Fix invalid JSON escape \s in Buildkite trigger comment regexes#3330
Conversation
\s is not a valid JSON escape sequence, causing a JSONDecodeError that prevented Buildkite from parsing the pipeline config entirely. No builds were triggering on any PR as a result. Replace \s with \\s throughout. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
cotti
approved these changes
May 3, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
\sinto JSON string values in.buildkite/pull-requests.org-wide.json, but\sis not a valid JSON escape sequenceJSONDecodeErroron parse, preventing Buildkite from reading the pipeline config at all — no builds were triggering on any PR\swith\\s(the correct way to embed a regex\sinside a JSON string)Unblocks #3328 and #3329.
Test plan
python3 -c "import json; json.load(open('.buildkite/pull-requests.org-wide.json'))"run docs-buildcomment on a PR triggers a Buildkite build🤖 Generated with Claude Code