Sentry-cli

Source Maps Upload Check "y-tho" (ongoing)

_Problem statement:_

Uploading source maps is a common source of frustration. Source maps are also one of the great value adds to our in
product experience. We want to automate supporting customers with frequent issues.

https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/

_Outcome: _

Developers will be provided with a tool to help them discover any issues they may have when uploading source maps

Sentry support will have a tool and docs to suggest to customers to hopefully first discover issues, and second at least
know what their problem is NOT.

_Key measurements:_

- qualitative: Is this useful for customers and support
- quantitative: Can we try to influence the number of Zendesk tickets
- quantitative: Can we influence the resolution time of source maps related Zendesk tickets

Can we find a way to track in zendesk the number of times the sentry-cli “y-tho“ functionality was useful

_Additional_

This is something users would run locally so I do not think we can track usage exactly what was not covered in y-tho

- Verify your source maps are built correctly
- Verify your source maps work locally
- Verify your source files are not too large
- this is a fuzzy requirement today in sentry
- Verify artifacts are not gzipped
- Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker)
- Should spit out an easily readable and easily copy and paste - to put into ZenDesk or elsewhere for support colleagues

_Possible second milestone:_

https://github.com/getsentry/rust-sourcemap/tree/master/cli

- In sentry error incorrect source map location
- this helps when producing sourcemaps locally then line and column
- this verify that it resolves locally
- if yes then it is a problem in between on sentry server side or upload
- 1st Verifies what you upload to sentry is exactly what you upload to sentry
- 2nd step from “y-tho” ensure previous steps are not for waste
- What is being automated?
- on release page you have your files (release artificats)
- download
- manually check the line number matches the error
- if correct then data is correct
- then you know an error with cli and not with the source maps that were uploaded

By: kamilogorek (1235)

Various fixes & improvements

- ref: Change comment format for find_matching_artifact (1243) by kamilogorek
- ref: Log correct AppCenter error message (1243) by kamilogorek
- fix: Respect no-zips option for debug files upload (1239) by saf-e
- chore: fix recommended VS Code extension name (1240) by vaind
- ref: Rename VERSION to SENTRY_CLI_VERSION in install readme (1227) by kamilogorek
- feat: Add organizations list command (1213) by kamilogorek
- docs(cli): Sync get-cli readme with our docs; add version specifier (1225) by kamilogorek
- test: Add integration tests for projects command (1212) by kamilogorek
- fix: replace git.io links with redirect targets (1209) by asottile-sentry

Various fixes & improvements

- ref: Prevent vercel/nft and similar tools from including binary file in their bundles (1207) by kamilogorek
- ref: Use node-fetchv2 for the simplicity sake (1206) by kamilogorek

Various fixes & improvements

- ref: Make `--header` a global flag so its position independent (1194)
- ref: Restore `monitors` as hidden command w. integration tests (1196)
- ref: Restore `bash-hook` as hidden command w. integration tests (1197)

Various fixes & improvements

- fix: Remove `fetch.FetchError` usage in favor of catch-all clause (1193) by kamilogorek
- ref: Restore and hide legacy aliases from 1.x for backward compatibility (1192) by kamilogorek

Various fixes & improvements

- fix: Allow hyphenated release names with any flags position (1187) by kamilogorek

This is the first, long-overdue major release in over 5 years of sentry-cli's life.
Some APIs were removed, some reworked, some newly added.

Most of introduced API changes are backward compatible through hidden aliases, so there is no immediate need for users
developing 3rd party tools to make all the changes immediatelly.
We do however encourage everyone to do it sooner or later, as deprecated items will be removed in the next major
releases.

Breaking changes are denotated with _(breaking)_ tag, and appropriate required changes are provided for each entry.

New APIs

- feat: Add `debug-files` command, which is a joined functionality of `difutil` and `upload-dif` commands.
- feat: Add `deploys` command, which was extracted from `releases deploys` subcommand.
- feat: Add `files` command, which was extracted from `releases files` subcommand.
- feat: Add `sourcemaps upload` command, which was extracted from `releases files upload-sourcemaps` subcommand.
- feat: Add `sourcemaps resolve` command.
- feat: Allow for specifying global `--header` argument, which supports multiple occurences, to configure outgoing
requests
- feat: Implement global `--quiet`/`--silent` flags to allow silencing `stdout` output (This flag is currently
implemented only for selected subcommands)

Removed APIs

- ref: Remove `react-native codepush` subcommand (use `react-native appcenter` instead) _(breaking)_
- ref: Remove `react-native-gradle` and `react-native-xcode` commands (use `react-native gradle` and
`react-native xcode` instead) _(breaking)_
- ref: Remove `crash_reporting` related code and `with_crash_reporting` crate feature (no required changes) _(breaking)_
- ref: Remove `SENTRY_NO_PROGRESS_BAR` env var in favor of `SENTRYCLI_NO_PROGRESS_BAR` (rename env variable) _(
breaking)_
- ref: Hide `difutil id` subcommand (use `debug-files check` instead)
- ref: Hide `upload-dsym` command (use `debug-files upload` instead)
- ref: Make `releases upload-sourcemaps --rewrite` a default behavior now
- ~ref: Remove `upload-dsym` command (use `debug-files upload` instead) _(breaking)_~ _restored in 2.0.2 as hidden
alias_
- ~ref: Remove `difutil id` subcommand (use `debug-files check` instead) _(breaking)_~ _restored in 2.0.2 as hidden
alias_
- ~ref: Remove `monitors` command (support for this feature has been dropped) _(breaking)_~ - _restored in 2.0.3 as
hidden command_
- ~ref: Remove `bash-hook` command (use `1.x` if you still need the functionality) _(breaking)_~ - _restored in 2.0.3 as
hidden command_

Breaking Changes

- ref: Update minimal required `node` version to `v12` (update node version) _(breaking)_
- ref: Rename `--header` argument of `releases files upload` command to `--file-header` (rename flag) _(breaking)_
- ref: Rename `CUSTOM_HEADER` to `SENTRY_HEADER` and `defaults.custom_header` to `http.header` (rename env variable or
update config file) _(breaking)_
- ref: Make `ignore-empty` for `releases set-commits` a default behavior and hide `--ignore-empty` flag (remove
`--ignore-empty` usage) _(breaking)_

Various fixes & improvements

- feat: Implement `--quiet` flag for `releases upload-sourcemaps` command
- feat: Implement `--quiet` flag for `difutil check` command
- ref: Make `--auth-token` a global argument
- ref: Make all `ProgressBar` instances and logs always write to `stderr`
- ref: Migrate error handling from `failure` to `anyhow` crate