Scope Vale linting for integration content

[theletterf]

Summary

• Restrict the integrations Vale workflow to user-facing package docs and metadata.
• Include fallback packages/*/docs/README.md files only when a package lacks _dev/build/docs/README.md.
• Opt integrations into YAML linting through .vale-overrides.ini.

Test plan

• actionlint .github/workflows/vale-lint.yml
• ruby -e \"require 'yaml'; YAML.load_file('.github/workflows/vale-lint.yml')\"
• Parsed .vale-overrides.ini with Python ConfigParser.

Fixes elastic/vale-rules#144

Made with Cursor

[theletterf]

@P1llus Please have a look.

[theletterf]

@mrodm Addressed the review feedback in 50c4401176:

• Moved github.repository and github.event.pull_request.number into GH_REPOSITORY and PR_NUMBER env vars before using them in the shell script.
• Switched the Vale workflow trigger, selector, and vale-paths patterns from packages/*/... to packages/**/... so future nested package paths are handled.
• Added .vale-overrides.ini to the Buildkite non-package-only skip lists in .buildkite/pull-requests.json and .buildkite/scripts/common.sh to avoid package test fan-out when only that override changes.

Validation run locally:

• actionlint .github/workflows/vale-lint.yml.
• ruby -e \"require 'yaml'; YAML.load_file('.github/workflows/vale-lint.yml')\" && jq empty .buildkite/pull-requests.json && bash -n .buildkite/scripts/common.sh.
• Simulated file selection for both packages/nginx/... and packages/observability/nginx/... paths.

[theletterf]

/test

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 50c4401

Failed CI Steps

• Check integrations netbox

[github-actions]

TL;DR

Buildkite Check integrations netbox failed in build 43625, but the captured log only contains teardown/upload output and a generic exit status 1, so the concrete failing test/assertion is not present in available evidence. Immediate action: inspect the uploaded netbox-system-*.xml test result artifact (or rerun with full step logs) to get the exact failure signature.

Remediation

• Download and inspect build/test-results/netbox-system-1779896786444958667.xml from build 43625 artifacts and identify the first failing testcase/error block.
• Apply a targeted fix based on that testcase, then re-run Check integrations netbox.

Investigation details

Root Cause

The provided step log is truncated to post-failure teardown and artifact upload, so root cause cannot be directly attributed to package code, test logic, dependency, or infra from this dataset alone.

PR #19235 changes are limited to:

• .github/workflows/vale-lint.yml
• .vale-overrides.ini
• .buildkite/pull-requests.json
• .buildkite/scripts/common.sh

No packages/netbox/** files are changed in this PR diff.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/43625
• Job/step: Check integrations netbox
• Log file: /tmp/gh-aw/buildkite-logs/integrations-check-integrations-netbox.txt
• Key log excerpt:

73. --- [netbox] failed
76. 🚨 Error: The command exited with status 1
78. user command error: exit status 1

• The same log confirms test result artifacts were uploaded, including:
  • build/test-results/netbox-system-1779896786444958667.xml
  • build/test-results/netbox-asset-1779896708215805379.xml
  • build/test-results/netbox-pipeline-1779896710092596960.xml

Verification

• Not run locally here; the actionable missing signal is the failing testcase/error payload from the uploaded XML artifact, which is not included in the captured log file.

Follow-up

If the failing testcase/error block is shared, it can be mapped directly to the responsible source path for a precise patch recommendation.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.