aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2024-05-17 17:27:44 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2024-05-21 11:03:22 +0300
commit57f6378aea619ceb07b935012772bd4698e6a2be (patch)
treec7df31f1386febf3ba570bc2e3cd2ef551ae68f5 /doc
parent19c8efe49f23569a53e928488c460e0d3b20cf8a (diff)
Add support for build_unloaded() notification for tenant-associated services
Diffstat (limited to 'doc')
-rw-r--r--doc/manual.cli10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index 2b96393..4d77dae 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -344,6 +344,7 @@ timestamp: <date-time>
[service-id]: <string>
[service-type]: <string>
[service-data]: <string>
+[service-action]: <action>
\
The \c{package} value can be repeated multiple times. The \c{timestamp} value
@@ -356,7 +357,14 @@ required information via some custom protocol, and expect the CI service to
notify it about the progress. In this case the third-party service type as
well as optionally the third-party id and custom state data can be
communicated to the underlying CI handler program via the respective
-\c{service-*} manifest values.
+\c{service-*} manifest values. Also note that normally a third-party service
+has all the required information (repository URL, etc) available at the time
+of the CI task initiation, in which case the \c{start} value is specified for
+the \c{service-action} manifest value. If that's not the case, the CI task is
+only pre-created at the time of the initiation without calling the CI handler
+program. In this case the CI handler is called later, when all the required
+information is asynchronously gathered by the service, and the \c{load} value
+is specified for the \c{service-action} manifest value.
\h#ci-overrides-manifest|CI Overrides Manifest|