Bump import job status expiration
What does this MR do?
This MR bumps Import's job status expiration from 15 to 24 hours as per request in #333252 (closed)
15 hours ceiling has been introduced 4 years ago 58371efb and project sizes grew since then with some projects taking longer than 15 hours to import.
~"group::import" is working on an alternative feature to Import/Export, GitLab Group Migration (that is going to be importing projects as well, only groups are supported now), https://docs.gitlab.com/ee/user/group/import/ which runs in a distributed fashion, instead of 1 sidekiq job, which should bring execution times for big projects down, as different top level relations are going to be imported concurrently.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team