Reschedule `latest_pipeline_id` population with all artifact types
What does this MR do?
This MR re-schedules a previously run migration with a missing artifact type called api_fuzzing and with a new artifact type called cluster_image_scanning.
The api_fuzzing artifact type was missing by mistake and the cluster_image_scanning type was introduced during the review process of the original MR so they also require this migration to be run again.
Related to #271408 (closed), !65280 (merged).
Database review
The existing migration has been marked as no-op and the remaining jobs are captured by Gitlab::BackgroundMigration.steal(There are no jobs left for GitLab.com though).
The migration will schedule background jobs for 2430 projects but we are not expecting all of them to be migrated.
rake db:migrate:up VERSION=20210713075117
== 20210729163312 ReScheduleLatestIdPopulationWithAllSecurityRelatedArtifactTypes: migrating
-- Scheduled 1 PopulateLatestPipelineIds jobs with a maximum of 100 records per batch and an interval of 120 seconds.
The migration is expected to take at least 120 seconds. Expect all jobs to have completed after 2021-07-29 16:48:04 UTC."
== 20210729163312 ReScheduleLatestIdPopulationWithAllSecurityRelatedArtifactTypes: migrated (0.4045s)rake db:migrate:down VERSION=20210713075117
== 20210729163312 ReScheduleLatestIdPopulationWithAllSecurityRelatedArtifactTypes: reverting
== 20210729163312 ReScheduleLatestIdPopulationWithAllSecurityRelatedArtifactTypes: reverted (0.0000s)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