1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
.. _available-workflows:
==================================
Available workflow implementations
==================================
Most workflows are mainly useful as sub-workflows of a more complex
workflow. The workflow that you are most likely to use directly is the
:workflow:`debian_pipeline` workflow.
As a user, you cannot directly execute a workflow implementation; instead,
you start them through a :ref:`workflow template
<explanation-workflow-template>`, which provides some default settings and
restricts those that you can set. These are configured by Debusine
instance admins, and are listed on the Workspace's details page. (e.g. for
`debusine.debian.net <https://debusine.debian.net/debian/developers/>`_).
.. toctree::
:glob:
specs/*
========================
Runtime status workflows
========================
The runtime status can have the following values (order of checks matters
here, first match defines the status):
- "Needs input": there's at least one child work request with task type
WAIT and status == RUNNING where ``workflow_data['needs_input']`` is true.
- "Running": there's at least one child work request with task type !=
WAIT and status == RUNNING.
- "Waiting": there's at least one child work request with task type
WAIT and status == RUNNING where ``workflow_data['needs_input']`` is false.
- "Pending": there's at least one child work request where status ==
PENDING.
- "Blocked": there's at least one child work request where status == BLOCKED.
- "Aborted": there's at least one child work request where status == ABORTED.
- "Completed": all the child work requests are in status COMPLETED.
The runtime status is accessible via ``workflow.workflow_runtime_status``.
|
