Enhance logging in all github import workers on raised exceptions

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

  • Close this issue

The following discussion from !70012 (merged) should be addressed:

  • @dstull started a discussion: (+4 comments)

    I'm not sure about this and other uses of fail_import that I've added ...

    What is the usual rule here on setting this to true or false?

Technical Note:

The labkit-ruby upgrade (part of upgrading to Ruby 3.0) injects info into logs - to track which deployment stage we execute on (main, cny)- after the event leaves gitlab-rails. Since it writes the stage log field, it overwrites any stage: value, so don't use this value in the logs. See !111590 (merged)

Edited Jul 29, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading