diff options
| author | Christopher Baines <mail@cbaines.net> | 2022-06-30 18:47:10 +0100 |
|---|---|---|
| committer | Christopher Baines <mail@cbaines.net> | 2022-06-30 20:50:19 +0100 |
| commit | 23504e0f01dc1eae05b307e313ba70faaad84be8 (patch) | |
| tree | 0831e28cd26a1bcb46da02580305901154b21471 /guix-build-coordinator/datastore.scm | |
| parent | 70c83f81db4a6dd9ad94d4ec2b3b3be62bd0f467 (diff) | |
| download | build-coordinator-23504e0f01dc1eae05b307e313ba70faaad84be8.tar build-coordinator-23504e0f01dc1eae05b307e313ba70faaad84be8.tar.gz | |
Support processing hook events in parallel
Forcing hooks to be sequential simplifies them, and the implementation, but it
doesn't always scale well. I'm particularly thinking about the build-submitted
hook and built-success hooks, the processing of which can back up if there's
lots of builds being submitted or finishing successfully.
This new functionality allows hooks to be processed in parallel, which should
allow to manage this more effectively.
Diffstat (limited to 'guix-build-coordinator/datastore.scm')
| -rw-r--r-- | guix-build-coordinator/datastore.scm | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/guix-build-coordinator/datastore.scm b/guix-build-coordinator/datastore.scm index 4aa2981..156e637 100644 --- a/guix-build-coordinator/datastore.scm +++ b/guix-build-coordinator/datastore.scm @@ -66,6 +66,7 @@ (re-export datastore-insert-unprocessed-hook-event) (re-export datastore-count-unprocessed-hook-events) (re-export datastore-list-unprocessed-hook-events) +(re-export datastore-find-unprocessed-hook-event) (re-export datastore-delete-unprocessed-hook-event) (re-export datastore-list-agent-builds) (re-export datastore-find-derivation) |