docker-compose: Add daily Trigger service

This change addresses the requirement to reduce the frequency of
creating Checkout Nodes instead of setting frequency limits on Maestro
Jobs (which might result in empty Checkouts in the Web Dashboard).

Configuration values in use do not provide a fix for the reported issue.
They were chosen to verify this approach on the Maestro Staging
instance. A tree has been selected using following criteria:

- adds as little as possible load for the Staging build cluster instance
- preferably has only one monitored branch which doesn't get updated often
- is related to the netdev tree already present in the Docker Compose deployment.

Resolves: kernelci/kernelci-core#2857

Signed-off-by: Paweł Wieczorek <pawiecz@collabora.com>

Author: pawiecz

docker-compose.yaml

@@ -135,6 +135,19 @@ services:
     extra_hosts:
       - "host.docker.internal:host-gateway"
 
+  trigger_daily:
+    <<: *base-service
+    container_name: 'kernelci-pipeline-trigger-daily'
+    command:
+      - './src/trigger.py'
+      - '--settings=${KCI_SETTINGS:-/home/kernelci/config/kernelci.toml}'
+      - 'run'
+      - '--poll-period=86400'
+      - '--trees=aaptel'
+      - '--name=trigger_daily'
+    extra_hosts:
+      - "host.docker.internal:host-gateway"
+
   timeout:
     <<: *base-service
     container_name: 'kernelci-pipeline-timeout'