Automatically increase build queued timeout for big number of builds in 'queued' notifications

Note that this commit changes the semantics of the tenant::queued_timestamp
member. Previously it was set to the time when the build objects are turned
into the queued state. Now it is set to the time when the queued notification
for them is assumed to be delivered to the third party service.

1 files changed, 14 insertions, 4 deletions

diff --git a/mod/module.cli b/mod/module.cli
index 57a5f31..f78cd06 100644
--- a/mod/module.cli
+++ b/mod/module.cli
@@ -305,13 +305,23 @@ namespace brep
          for the \cb{build-hard-rebuild-timeout} option."
       }
 
-      size_t build-queued-timeout = 30
+      size_t build-queued-timeout = 15
       {
         "<seconds>",
-        "Time to wait before assuming the \cb{queued} notifications are
+        "Time to wait before assuming the \cb{queued} notification batch is
          delivered for package CI requests submitted via third-party services
-         (GitHub, etc). During this time a package is not considered for a
-         build. Must be specified in seconds. Default is 30 seconds."
+         (GitHub, etc). Until all such batches are delivered, a package is
+         not considered for a build. Must be specified in seconds. Default
+         is 15 seconds. See also \cb{build-queued-batch}."
+      }
+
+      size_t build-queued-batch = 60
+      {
+        "<num>",
+        "The maximum number of build configurations in the \cb{queued}
+         notification batch for package CI requests submitted via third-party
+         services (see \cb{build-queued-timeout} for details). The default
+         is 60."
       }
     };