Simone Gotti afae185e11 *: rework run approval and annotations ... * runservice: use generic task annotations instead of approval annotations * runservice: add method to set task annotations * gateway: when an user call the run task approval action, it will set in the task annotations the approval users ids. The task won't be approved. * scheduler: when the number of approvers meets the required minimum number (currently 1) call the runservice to approve the task In this way we could easily implement some approval features like requiring a minimum number of approvers (saved in the task annotations) before marking the run as approved in the runservice.		2019-05-06 15:19:29 +02:00
..
action	*: rework run approval and annotations	2019-05-06 15:19:29 +02:00
api	*: rework run approval and annotations	2019-05-06 15:19:29 +02:00
common	runservice: move all scheduler etcd data to own dir	2019-04-27 08:59:47 +02:00
readdb	runservice readdb: get run from ost db if it's not in run db	2019-05-06 14:55:10 +02:00
store	runservice: check changegroup name	2019-04-29 10:12:34 +02:00
scheduler_test.go	runservice scheduler: take a copy of run in advanceRunTasks	2019-04-17 18:06:31 +02:00
scheduler.go	runservice: rename command(handler) to action(handler)	2019-05-03 23:59:21 +02:00