mirrors/forgejo-docs
1
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2025-04-26 13:40:30 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

{admin,user}: actions: update log & artifact storage & usage

Browse source
This commit is contained in:
Earl Warren 2023-09-29 16:53:00 +02:00
parent d0c10d5716
commit f543af1e87
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
4 changed files with 79 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

33
docs/admin/actions.md
View file

@ -43,6 +43,39 @@ As of `Forgejo v1.21` it is enabled by default. It can be disabled by adding the
ENABLED = false
```
### Storage
The logs and artifacts are stored in `Forgejo`. The cache is stored by
the runner itself and never sent to `Forgejo`.
#### `job` logs
The logs of each `job` run is stored by the `Forgejo` server and never
expires. The location where these files are stored is configured in
the `storage.actions_log` section of `app.ini` as [explained in in the
storage documentation](../storage/).
#### `artifacts` logs
The artifacts uploaded by a job are stored by the `Forgejo` server and
expire after a delay that defaults to 90 days and can be configured as
follows:
```yaml
[actions]
ARTIFACT_RETENTION_DAYS = 90
```
The location where these artifacts are stored is configured in
the `storage.artifacts` section of `app.ini` as [explained in in the
storage documentation](../storage/).
The `admin/monitor/cron` administration web interface can be used to
manually trigger the expiration of artifacts instead of waiting for
the scheduled task to happen.
![cleanup logs and artifacts](../_images/user/actions/actions-cleanup.png)
## Forgejo runner
The `Forgejo runner` is a daemon that fetches workflows to run from a