GitLab

We want to save some files created on the target after a test (or at least a job) is done.

At the moment this is only possible using a third party storage as described here: https://docs.lavasoftware.org/lava/publishing-artifacts.html

We would like to avoid using a third party storage and fiddling around with (temporary) access tokens but be able to store the relevant files in the artifacts of the ci pipelines that triggered the lava job.

I would imagine something like this but I am not that deep into Lava:

• The user defines some artifacts in the job definition.
• The worker copies the defined files from the DUT after the job is done if the connection supports it. (A first step could be to support this for FVP devices using the changes that allow to mount an artifacts folder. !1354)
• The worker compresses artifact and posts the archive to the rest api of the master.
• The user can download the files via rest api, webinterface or lava-cli from the master.

Are there any ideas, opinions or related discussions on this?