Add analytics-cli upload troubleshooting and update install path#54
Open
samgutentag wants to merge 1 commit into
Open
Add analytics-cli upload troubleshooting and update install path#54samgutentag wants to merge 1 commit into
samgutentag wants to merge 1 commit into
Conversation
samgutentag
added
the
needs review
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Member
Author
|
Verification status (2026-05-29): Verified: customers can use this. Ready to publish.
Ready to publish after editorial review of the flagged items (Bazel BEP JSON parser status, validate attribution, install path messaging). |
samgutentag
added
ready to merge
…ias 403, validate warnings
samgutentag
force-pushed
the
sam-gutentag/analytics-cli-troubleshooting
branch
from
f411935 to
4f3ae41
Compare
Member
Author
|
Verification status (May 31, 2026): analytics-cli troubleshooting docs cover the existing, shipped CLI — no flag or eng dependency.
Next action: merge this PR. Generated by Claude Code |
Member
Author
|
Docs Verify Sweep · June 1, 2026 · ✅ live Feature is live in production. Ready to merge. Unchanged from previous sweep (May 31, 2026). Generated by Claude Code |
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
1 participant
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
flaky-tests/reference/cli-reference.mdxcovering the four most-repeated upload issues from customer Slack: "no tests found" (Playwright/Storybook aborts, Bazel BEP JSON, empty globs), 403 from SSH-alias repo-URL inference,validate"name too short"/"classname too short" warnings, and how to useuploadwhen post-processing JUnit XML from an external runner.trunk-analytics-cliinstall path isgithub.com/trunk-io/analytics-cli/releases, notget.trunk.io/trunk.io/releases(which install the legacy launcher used by Code Quality).uploadvstestInfo callout in the Running and Quarantining section so customers wrapping an external runner pick the right command on the first try.Why
Sourced from customer feedback mining (cluster
analytics-cli-upload-edge-cases, verdictpartial, 9 pairs across 6 customers, first-class IA candidate). The CLI reference documents the happy path; customers hit recurring upload issues that have well-known workarounds but no documented troubleshooting surface.Items flagged for review
validatesource attribution. The page says Trunk does not yet surface the originating file for "name too short" / "classname too short" warnings. Confirm whether better attribution has shipped before merge, and update if so.get.trunk.io/trunk.io/releasesas legacy for Flaky Tests purposes. Confirm this framing is accurate and doesn't conflict with Code Quality docs.flaky-tests/reference/cli-troubleshooting.mdxlater.Customer signal
analytics-cli-upload-edge-cases(verdict: partial, 9 pairs / 6 customers, first-class IA candidate)findings/clusters/analytics-cli-upload-edge-cases.json):