Open Bug 1806578 Opened 2 years ago Updated 10 months ago

write a symbol uploader client

Categories

(Tecken :: Upload, task, P3)

Tracking

(Not tracked)

People

(Reporter: willkg, Unassigned)

References

Details

Uploading symbols is tricky enough that it might be easier on everyone if we write a symbol uploader command line client.

This would make it easier for us to have a well-tested symbol uploader client rather than a bunch of semi-tested clients. This would make it easier for new and existing products to include symbol uploading in their build process. This would make it easier for Tecken engineers to adjust the API for uploading symbols because we own both sides.

Some thoughts along those lines:

  • it would set a user agent
  • it would require a symbols.mozilla.org auth token
  • it would handle retrying the upload in appropriate circumstances
  • maybe you'd point it at a directory tree and it would assemble multiple zip files smaller than some specified size and upload them serially
  • maybe it would handle compression of things (the entire file, individual files by type, etc)
  • maybe it would validate sym files
  • maybe it would drop unsupported files so they're not uploaded
  • maybe it would put all the files in the right place in the zip file while assembling the zip file (e.g. sym files need to be in DEBUGFILENAME/DEBUGID/SYMFILE tree)

Tecken is in Python and we have Python in the tree, so Python might be a good language. Maybe we could provide self-contained "executables" using nuitka.

dump_syms and friends are all in Rust, so Rust might be a good language.

This bug covers figuring out whether this is worth pursuing, who is interested in advising/contributing/testing, and writing out a spec for a minimal viable prototype.

Good idea, we've got a lot of duplication here, from ad-hoc Python stuff to bash-calls-zip-and-curl-on-this-folder.

See Also: → 1898749
You need to log in before you can comment on or make changes to this bug.