Increase max runtime for direct placeholder reassignment
What does this MR do and why?
A maximum execution runtime was implemented for the Direct Reassign process to prevent the job from running for an extended period.
The current 60-second runtime limit is insufficient, leading to the reassignment process restarting multiple times.
For example, tests on GitLab.com revealed that reassigning just a few contributions from a placeholder can cause the reassign process to restart 2 or 3 times. This happens because executing the update queries across all affected tables takes approximately 30 seconds, as more than 40 queries must be run.
This update extends the maximum runtime to 5 minutes, providing sufficient time to process additional records and tables while avoiding excessively long execution periods.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
- Enable the
user_mapping_direct_reassignmentFF - Stage a direct transfer migration of a group with projects on your localhost. Ensure the group and/or project have contributions (MRs, issues, etc).
- After the import, reassign some of the contributions of a source user to a real user, and then as that user, accept the contribution assignment.
- During the contribution reassignment process, the user should become the owner of the contributions.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.