foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-12-26 22:51:22 -05:00
Code Issues Activity

user: actions: document jobs.<job_id>.needs option

Browse source 
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
This commit is contained in:
Christoph Heiss 2024-11-30 10:18:18 +01:00
parent 660547d454
commit 18cfae1d78
No known key found for this signature in database
GPG key ID: 73D5E7FDEE3DE49A
1 changed files with 22 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
docs/user/actions.md
View file

@ -711,7 +711,7 @@ and its content defines the sequential `step`s to be run.
Each job runs in a different container and shares nothing with other jobs.
All jobs run in parallel, unless they depend on each other as specified with `needs`.
All jobs run in parallel, unless they depend on each other as specified with [`jobs.<job_id>.needs`](#jobsjob_idneeds).
### `jobs.<job_id>`
@ -740,6 +740,27 @@ The `runs-on: lxc` label will run the jobs in a [LXC](https://linuxcontainers.or
The `runs-on: self-hosted` label will run the jobs directly on the host, in a shell spawned from the runner. It provides no isolation at all.
### `jobs.<job_id>.needs`
Can be used to introduce ordering between different jobs by listing their respective `<job_id>`. All jobs listed here must complete successfully before this job is considered for execution.
`needs` can either be a single string, naming a single job as pre-requisite, or an array for specifying multiple jobs to run before this one.
For instance:
```yaml
---
jobs:
lint:
steps:
- run: echo linting the code
build:
needs:
- job1
steps:
- run: echo only run after linting
```
### `jobs.<job_id>.strategy.matrix`
If present, it will generate a matrix from the content of the object