From 5b71180cb97a9a79b40b3fd025dfe17a48712848 Mon Sep 17 00:00:00 2001 From: Mattia Rizzolo Date: Mon, 14 Dec 2015 18:34:01 +0000 Subject: reproducible: don't save the reschedule reason in the DB That was actually a bad idea, given that we don't check on input execute the with the given string right away. Also, we're not really interested in this, so once convenient we can also remove the column from the DB. --- bin/reproducible_remote_scheduler.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'bin/reproducible_remote_scheduler.py') diff --git a/bin/reproducible_remote_scheduler.py b/bin/reproducible_remote_scheduler.py index 331f7b36..4afe29db 100755 --- a/bin/reproducible_remote_scheduler.py +++ b/bin/reproducible_remote_scheduler.py @@ -233,7 +233,6 @@ if amount + len(ids) > 200 and not local: to_schedule = [] save_schedule = [] artifacts_value = 1 if artifacts else 0 -reason = reason if reason else None if notify_on_start: do_notify = 2 elif notify or artifacts: @@ -242,7 +241,7 @@ else: do_notify = 0 for id in ids: to_schedule.append((id, date, artifacts_value, str(do_notify), requester, - reason)) + None)) save_schedule.append((id, requester, epoch)) log.debug('Packages about to be scheduled: ' + str(to_schedule)) -- cgit v1.2.3-70-g09d2