runbot/runbot_merge/data
Xavier Morel 029957dbeb [IMP] *: trigger-ify task queue type crons
These are pretty simple to convert as they are straightforward: an
item is added  to a work queue (table), then a cron regularly scans
through the table executing the items and deleting them.

That means the cron trigger can just be added on `create` and things
should work out fine.

There's just two wrinkles in the port_forward cron:

- It can be requeued in the future, so needs a conditional trigger-ing
  in `write`.
- It is disabled during freeze (maybe something to change), as a
  result triggers don't enqueue at all, so we need to immediately
  trigger after freeze to force the cron re-enabling it.
2024-08-02 15:14:50 +02:00
..
merge_cron.xml [IMP] *: trigger-ify task queue type crons 2024-08-02 15:14:50 +02:00
runbot_merge.pull_requests.feedback.template.csv [CHG] forwardport: notify the outstanding forwardports rather than source 2024-06-04 08:56:51 +02:00