Increase Interruption Limit for Bitbucket Import Jobs and Improve Failed Status Handling

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

• Work on this issue
• Close this issue

Current Behavior

• Bitbucket Cloud and Server stage workers have a default maximum interruption limit of 3
• Jobs get placed in dead queue after reaching the interruption limit
• Migration status only changes to failed after 24 hours via Gitlab::Import::StuckImportJob

Problem

When Bitbucket import jobs are interrupted multiple times, they are moved to the dead queue even though they could eventually complete successfully. Additionally, users must wait 24 hours before seeing the failed status.

Proposed Solution

1. Increase the maximum interruption limit for Bitbucket Cloud and Server workers (similar to GitHub Import)
2. Implement sidekiq_interruptions_exhausted callback in the jobs to mark migration status as failed immediately when the max interruption limit is reached.

Expected Outcome

• Fewer jobs will end up in the dead queue
• Users will receive immediate feedback when imports fail due to exhausted interruptions
• Better overall import reliability for Bitbucket repositories