From a6a82633e508503b4e40748809fdfa9d9988e9c4 Mon Sep 17 00:00:00 2001 From: Tobias Lippert Date: Thu, 14 Sep 2023 17:15:35 +0200 Subject: [PATCH] change cron expression to production value again --- .../artemis/service/scheduled/DataExportScheduleService.java | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/main/java/de/tum/in/www1/artemis/service/scheduled/DataExportScheduleService.java b/src/main/java/de/tum/in/www1/artemis/service/scheduled/DataExportScheduleService.java index 1d7eebb0a844..8278387c1efe 100644 --- a/src/main/java/de/tum/in/www1/artemis/service/scheduled/DataExportScheduleService.java +++ b/src/main/java/de/tum/in/www1/artemis/service/scheduled/DataExportScheduleService.java @@ -56,9 +56,7 @@ public DataExportScheduleService(DataExportRepository dataExportRepository, Data * Created will be all data exports that are in the state REQUESTED OR IN_CREATION * Deleted will be all data exports that have a creation date older than seven days */ - // TODO change again after testing. As long as we do not use this cron expression one server test always fails - // @Scheduled(cron = "${artemis.scheduling.data-export-creation-time: 0 0 4 * * *}") - @Scheduled(cron = "0 */10 * * * *") + @Scheduled(cron = "${artemis.scheduling.data-export-creation-time: 0 0 4 * * *}") public void createDataExportsAndDeleteOldOnes() throws InterruptedException { if (profileService.isDev()) { // do not execute this in a development environment