Module: CronjobChildWorker
- Extended by:
- ActiveSupport::Concern
- Included in:
- Analytics::UsageTrends::CounterJobWorker, Ci::DeleteObjectsWorker, Ci::DestroyOldPipelinesWorker, Ci::UnlockPipelinesInQueueWorker, CleanupContainerRepositoryWorker, ContainerRegistry::DeleteContainerRepositoryWorker, ContainerRegistry::RecordDataRepairDetailWorker, DependencyProxy::CleanupManifestWorker, Members::ExpiringEmailNotificationWorker, Members::PruneDeletionsWorker, MergeRequestCleanupRefsWorker, Packages::Cleanup::ExecutePolicyWorker, Packages::CleanupArtifactWorker, PagesDomainSslRenewalWorker, PagesDomainVerificationWorker, Projects::InactiveProjectsDeletionNotificationWorker, Projects::RefreshBuildArtifactsSizeStatisticsWorker, Releases::CreateEvidenceWorker, RepositoryCheck::BatchWorker, VirtualRegistries::Packages::Cache::DestroyOrphanEntriesWorker
- Defined in:
- app/workers/concerns/cronjob_child_worker.rb
Overview
Cronjobs that call other cronjobs should have their own tag so that we can isolate cron activity to make end-to-end code mappings better.