mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-12-27 19:00:35 +00:00
Document how to enable parallel step exec for all steps (#3605)
Document how depends_on work in more details --------- Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com> Co-authored-by: Anbraten <6918444+anbraten@users.noreply.github.com>
This commit is contained in:
parent
b0c9dfd2cf
commit
399bc5bf1b
2 changed files with 30 additions and 2 deletions
|
@ -50,7 +50,8 @@ git commit -m "updated README [CI SKIP]"
|
|||
|
||||
## Steps
|
||||
|
||||
Every step of your workflow executes commands inside a specified container. The defined commands are executed serially.
|
||||
Every step of your workflow executes commands inside a specified container.<br>
|
||||
The defined steps are executed in sequence by default, if they should run in parallel you can use [`depends_on`](./20-workflow-syntax.md#depends_on).<br>
|
||||
The associated commit is checked out with git to a workspace which is mounted to every step of the workflow as the working directory.
|
||||
|
||||
```diff
|
||||
|
@ -484,6 +485,19 @@ Normally steps of a workflow are executed serially in the order in which they ar
|
|||
- go test
|
||||
```
|
||||
|
||||
:::note
|
||||
You can define a step to start immediately without dependencies by adding an empty `depends_on: []`. By setting `depends_on` on a single step all other steps will be immediately executed as well if no further dependencies are specified.
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
- name: check code format
|
||||
image: mstruebing/editorconfig-checker
|
||||
depends_on: [] # enable parallel steps
|
||||
...
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
### `volumes`
|
||||
|
||||
Woodpecker gives the ability to define Docker volumes in the YAML. You can use this parameter to mount files or folders on the host machine into your containers.
|
||||
|
|
|
@ -50,7 +50,8 @@ git commit -m "updated README [CI SKIP]"
|
|||
|
||||
## Steps
|
||||
|
||||
Every step of your workflow executes commands inside a specified container. The defined commands are executed serially.
|
||||
Every step of your workflow executes commands inside a specified container.<br>
|
||||
The defined steps are executed in sequence by default, if they should run in parallel you can use [`depends_on`](./20-workflow-syntax.md#depends_on).<br>
|
||||
The associated commit is checked out with git to a workspace which is mounted to every step of the workflow as the working directory.
|
||||
|
||||
```diff
|
||||
|
@ -478,6 +479,19 @@ Normally steps of a workflow are executed serially in the order in which they ar
|
|||
- go test
|
||||
```
|
||||
|
||||
:::note
|
||||
You can define a step to start immediately without dependencies by adding an empty `depends_on: []`. By setting `depends_on` on a single step all other steps will be immediately executed as well if no further dependencies are specified.
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
- name: check code format
|
||||
image: mstruebing/editorconfig-checker
|
||||
depends_on: [] # enable parallel steps
|
||||
...
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
### `volumes`
|
||||
|
||||
Woodpecker gives the ability to define Docker volumes in the YAML. You can use this parameter to mount files or folders on the host machine into your containers.
|
||||
|
|
Loading…
Reference in a new issue