Set BulkImports::Tracker as skipped if entity is failed
What does this MR do and why?
This MR updates instance of BulkImports::Tracker to be skipped instead of failed in order to not create a flood of database BulkImports::Failure records. Because a BulkImports::Entity (a project or a group) can have many 'relation migration' trackers (e.g. issues tracker, merge requests tracker, labels tracker, etc), if an entity is marked as failed, each relation tracker creates the same failure db record, making it harder for users to figure out what went wrong during the migration. This MR updates trackers to be skipped, avoiding records in the database and making it cleaner and clearer into what went wrong.
Screenshots or screen recordings
| before | after |
|---|---|
 |
 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.