Docs feedback: Unclear what job artifacts does Job Artifacts API operate on
When looking at https://docs.gitlab.com/ee/api/job_artifacts.html#delete-artifacts
the description is very simple:
Delete artifacts of a job.
When you compare it with example output of https://docs.gitlab.com/ee/api/jobs.html#get-a-single-job as well as read through https://docs.gitlab.com/ee/api/jobs.html#erase-a-job however it becomes clear that:
- Job traces (logs) are also considered job artifacts and this REST API endpoint doesn't delete them.
- What https://docs.gitlab.com/ee/ci/yaml/#artifacts describes as "artifacts" are in fact
archive
artifacts from the REST - There are other types of job artifacts, e.g.
metadata
,junit
seem to be inaccessible entirely but still there
From data retention perspective, it is not clear:
- what types of artifacts does the Job Artifacts API operate on
- how to delete them and access them? e.g. does
delete-artifacts
removejunit
reports? - is release evidence also an artifact and does it get removed?
Edited by Waldek Maleska