Skip to content

Avoid storing backtraces from Bitbucket Cloud imports in the database

Stan Hu requested to merge sh-clean-up-bitbucket-import-errors into master

We noticed in gitlab-com/gl-infra/production#908 (closed) some Bitbucket imports took over a second to load their projects row because import_error was huge due to errors. To prevent this, we now:

  1. Clean the backtraces
  2. Log the details into importer.log
  3. Omit the details from the database

Note that we don't clear out the import_error yet, so existing imports will still have this data.

Edited by Stan Hu

Merge request reports