feat(build): Improve error messages for nonexistent projects#2753
feat(build): Improve error messages for nonexistent projects#2753runningcode wants to merge 3 commits intomasterfrom
Conversation
bd9e1c2 to
3c46d63
Compare
When build upload fails due to nonexistent project or organization, now provides clearer error messages with specific guidance: - Shows "Project not found" with guidance to check --project and --org flags - Shows "Organization not found" with guidance to check --org flag - Preserves original error messages for other error types Resolves EME-175: Missing error message on build upload with nonexistent project 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
When 'sentry-cli build upload' fails due to a nonexistent project, provide specific guidance to users about using --project and --org flags. Fixes EME-175
9ee0e81 to
1235c29
Compare
|
@runningcode What's wrong with the existing output? If you run this code against This does not mention the specific flags, but given that there are multiple ways of specifying orgs and projects, and given that we use this same error message everywhere else in Sentry CLI, I am not sure we need to add a specific additional message only for the EME-175 appears to have been opened before the error message was added to the warning line. I would argue that the general warning should be sufficient to resolve that issue. |
|
Yes you're right we don't need this PR. The error message was already improved on the backend. The still existing bad message is when the org is non-existant though. I'll need to fix that.
|
Summary
sentry-cli build uploadfails due to nonexistent projects--projectand--orgflagsChanges
src/commands/build/upload.rsto detect "Project not found" errorscommand_build_upload_nonexistent_projectwith mock endpointsFixes EME-175