Avoid storing backtraces from Bitbucket Cloud imports in the database
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:
- Clean the backtraces
- Log the details into importer.log
- 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