When AdvanceStage workers exhaust their retries, they should enact their timeout_strategy

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Problem

Currently when AdvanceStageWorkers exhaust their Sidekiq retries, the import will get stuck.

This affects the following importers which have AdvanceStageWorkers:

• Bitbucket Cloud
• Bitbucket Server
• GitHub
• Jira issue importer

Proposal

AdvanceStageWorkers mixin the Gitlab::Import::AdvanceStage module, which has logic #422979 (closed) to either advance to the next stage or fail the import.

We could add the sidekiq_retries_exhausted hook to AdvanceStage to enact this when its retries have been exhausted.

This would mean when an AdvanceStageWorker exhausted its retries it would either advance to the next stage, or fail the import.