Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: missing info for runs_on #2457

Merged
merged 4 commits into from
Sep 13, 2023
Merged

docs: missing info for runs_on #2457

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0f2fce8
docs: missing info for runs_on
lonix1 Sep 13, 2023
3a93fe5
fix
lonix1 Sep 13, 2023
a912982
fix
lonix1 Sep 13, 2023
c343057
Merge branch 'main' into patch-1
qwerty287 Sep 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/versioned_docs/version-1.0/20-usage/20-pipeline-syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -901,6 +901,10 @@ when:

Woodpecker supports to define multiple workflows for a repository. Those workflows will run independent from each other. To depend them on each other you can use the [`depends_on`](./25-workflows.md#flow-control) keyword.

## `runs_on`

Workflows that should run even on failure should set the `runs_on` tag. See [here](./25-workflows.md#flow-control) for an example.

## Privileged mode

Woodpecker gives the ability to configure privileged mode in the YAML. You can use this parameter to launch containers with escalated capabilities.
Expand Down