gitea_runner: Fix yamllint errors
This commit is contained in:
parent
ec5d54730d
commit
1d8ab7aa52
1 changed files with 13 additions and 7 deletions
|
@ -1,3 +1,4 @@
|
|||
---
|
||||
log:
|
||||
# The level of logging, can be trace, debug, info, warn, error, fatal
|
||||
level: info
|
||||
|
@ -11,8 +12,9 @@ runner:
|
|||
# It will be ignored if it's empty or the file doesn't exist.
|
||||
env_file: .env
|
||||
# The timeout for a job to be finished.
|
||||
# Please note that the Gitea instance also has a timeout (3h by default) for the job.
|
||||
# So the job could be stopped by the Gitea instance if it's timeout is shorter than this.
|
||||
# Please note that the Gitea instance also has a timeout (3h by default)
|
||||
# for the job. So the job could be stopped by the Gitea instance if it's
|
||||
# timeout is shorter than this.
|
||||
timeout: 3h
|
||||
# Whether skip verifying the TLS certificate of the Gitea instance.
|
||||
insecure: false
|
||||
|
@ -28,17 +30,21 @@ cache:
|
|||
# If it's empty, the cache data will be stored in $HOME/.cache/actcache.
|
||||
dir: ""
|
||||
# The host of the cache server.
|
||||
# It's not for the address to listen, but the address to connect from job containers.
|
||||
# So 0.0.0.0 is a bad choice, leave it empty to detect automatically.
|
||||
# It's not for the address to listen, but the address to connect from job
|
||||
# containers. So 0.0.0.0 is a bad choice, leave it empty to detect
|
||||
# automatically.
|
||||
host: ""
|
||||
# The port of the cache server.
|
||||
# 0 means to use a random available port.
|
||||
port: 0
|
||||
|
||||
container:
|
||||
# Which network to use for the job containers. Could be bridge, host, none, or the name of a custom network.
|
||||
# Which network to use for the job containers. Could be bridge, host, none,
|
||||
# or the name of a custom network.
|
||||
network_mode: bridge
|
||||
# Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
|
||||
# Whether to use privileged mode or not when launching task containers
|
||||
# (privileged mode is required for Docker-in-Docker).
|
||||
privileged: false
|
||||
# And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).
|
||||
# And other options to be used when the container is started
|
||||
# (eg, --add-host=my.gitea.url:host-gateway).
|
||||
options:
|
||||
|
|
Loading…
Add table
Reference in a new issue