From d075b4d0f93f8576836ebf73b123df12e3f39da0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= <ludo@gnu.org>
Date: Sat, 7 Oct 2023 17:41:35 +0200
Subject: [PATCH] =?UTF-8?q?doc:=20Add=20=E2=80=9CTriggering=20an=20Evaluat?=
 =?UTF-8?q?ion=E2=80=9D=20section.?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* doc/cuirass.texi (Triggering an Evaluation): New section.
---
 doc/cuirass.texi | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/doc/cuirass.texi b/doc/cuirass.texi
index 69c58f7..5c70946 100644
--- a/doc/cuirass.texi
+++ b/doc/cuirass.texi
@@ -926,6 +926,20 @@ Only consider evaluations that are part of the given @code{spec}
 specification.
 @end table
 
+@section Triggering an Evaluation
+
+@cindex evaluation trigger
+One can send an HTTP @code{POST} request to trigger the evaluation of a
+jobset, along these lines:
+
+@example
+wget --post-data="" -O /dev/null \
+  https://cuirass.example.org/@var{jobset}/hooks/evaluate
+@end example
+
+A good idea is to do that from the post-push hook of the relevant Git
+repository.
+
 @section Build information
 
 It is possible to query Cuirass web server for build informations. The