Quick start: check what Pipelines can do here in three steps

After these three steps you'll know whether runs can execute on your installation, and what you can still use if they can't. Takes about five minutes.

Before you begin

wkdopipelines, wkdocore, wkdostorage, and wkcore are installed and enabled.
A project, and an account with at least the Reader role in it.
For step 3: the wiki administrator account.

Step 1: Look for the area

Open the project's start page and check the project rail.

Pipelines is listed: a plugin registers pwsh.catalog and pwsh.runner, so runs can execute.
Pipelines is missing: there's no runner – the state the product ships in. Go on to step 2 anyway.

Step 2: Open the screen by address

Add &do=wkdopipelines to the address of the project's start page, for example:

/doku.php?id=en:projects:acme:start&do=wkdopipelines

You'll see the project's pipelines. On a fresh installation the screen says: No pipelines defined for this project yet. The product offers no way to create one.

Step 3: Read a run, if there is one

If a pipeline exists, open its run history and then one of its runs. Each log line shows where it came from:

Line	Source
no prefix	the script's standard output
`[err] …`	the script's standard error
`[sys] …`	the runner's own account

Without a runner, a run that the wiki administrator starts with Run now ends as failed with exactly one line: [sys] pwsh runner is unavailable (plugin not loaded).

Check the result

You know whether a runner is present.
You know the project's pipelines and runs – or that there aren't any.
A missing Pipelines area is what you should expect without a runner; it isn't an error.

Next steps

wkdopipelines – reference: visibility, permissions, the log, and limitations.
wkdodashboard – a project's landing page.